test

[hamid97m]

Summary by Sourcery

Add a selectedDate parameter to HeroDatePicker to set the initial selected date.

New Features:

• Allow setting an initial selected date in HeroDatePicker.

Tests:

• Add tests for the new selectedDate parameter.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request introduces a new parameter to the HeroDatePicker composable function, selectedDate, which allows the user to set the initial selected date. It also modifies the way the initial selected date is handled within the composable.

Sequence diagram for date initialization flow

sequenceDiagram
    participant C as Client
    participant H as HeroDatePicker
    participant S as ShamsiDatePickerUtil

    C->>H: Create with selectedDate
    H->>S: gregorianToPersian(selectedDate)
    S-->>H: Return Shamsi date
    H->>H: Initialize state with Shamsi date
    H-->>C: onSelectedDateChange callback

Loading

Class diagram for HeroDatePicker composable function changes

classDiagram
    class HeroDatePicker {
        +HeroDatePicker(modifier: Modifier)
        +HeroDatePicker(selectedDate: Date)
        +HeroDatePicker(selectableYearRange: Iterable<Int>)
        +HeroDatePicker(isSelectFromFutureEnable: Boolean)
        +HeroDatePicker(textStyle: TextStyle)
        +HeroDatePicker(onSelectedDateChange: (SelectedDate) -> Unit)
    }
    note for HeroDatePicker "New selectedDate parameter added"

    class SelectedDate {
        +year: Int
        +month: Int
        +day: Int
    }

Loading

File-Level Changes

Change	Details	Files
Added a new parameter to the HeroDatePicker composable function to set the initial selected date.	Added selectedDate parameter to the HeroDatePicker composable function. Modified the LaunchedEffect to use the selectedDate parameter to set the initial selected date. Modified the selectedYear, selectedMonth, and selectedDay to use the selectedDate parameter to set the initial selected date.	HeroDatePicker/src/main/java/com/hamid97m/herodatepicker/view/HeroDatePicker.kt
Updated the README.md file to include a description of the new parameter and a sample app.	Added a description of the new selectedDate parameter. Added a link to the sample app. Added a screenshot of the library.	README.md
Added a deepsource.toml file to configure the DeepSource analysis.	Added a deepsource.toml file to configure the DeepSource analysis.	.deepsource.toml
Added a LICENSE file to the project.	Added a LICENSE file to the project.	LICENSE

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[deepsource-io]

Here's the code health analysis summary for commits ae50f3f..752337d. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Java	✅ Success		View Check ↗
Kotlin	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[sourcery-ai]

Hey @hamid97m - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟡 General issues: 2 issues found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue: LaunchedEffect should depend on selectedDate to handle parameter updates properly.

Currently, changes to selectedDate won't trigger an update of the initial selection. Change Unit to selectedDate to ensure the effect runs when the parameter changes.

[sourcery-ai]

issue: Add validation for selectedDate against isSelectFromFutureEnable constraint.

If isSelectFromFutureEnable is false but selectedDate is in the future, this creates an inconsistent state. Consider adding validation at the start of the composable.