feat: add i18n support to InlineDatePicker

[javier-godoy]

Close #82

Summary by CodeRabbit

• New Features

  • Introduced internationalization support for the Inline Date Picker, allowing users to customize language settings.
  • Added a new method to set i18n properties for enhanced localization.

• Improvements

  • Streamlined the assignment of i18n properties in the Inline Date Picker for better readability and maintainability.

• Chores

  • Updated copyright year to 2024 across relevant files.

[coderabbitai]

Walkthrough

The changes involve an update to the pom.xml version number for the year-month-calendar project, the introduction of internationalization (i18n) support in the InlineDatePicker class, and enhancements to the related JavaScript file for better i18n property assignment. Additionally, updates were made to the InlineDatePickerDemo class, including a copyright year change and conditional compilation for the LocaleSelector component.

Changes

Files	Change Summary
pom.xml	Updated version from 4.2.2-SNAPSHOT to 4.3.0-SNAPSHOT.
src/main/java/com/flowingcode/addons/ycalendar/InlineDatePicker.java	Added setI18n(DatePickerI18n i18n) method for i18n support; updated copyright year; added imports.
src/main/resources/META-INF/frontend/fc-inline-date-picker/fc-inline-date-picker.js	Modified i18n property assignment to use an array and forEach method for improved readability.
src/test/java/com/flowingcode/addons/ycalendar/InlineDatePickerDemo.java	Updated copyright year; added conditional compilation for LocaleSelector based on Vaadin version.

Assessment against linked issues

Objective	Addressed	Explanation
Add i18n support to InlineDatePicker (#82)	✅

🐰 Hopping through the code so bright,
With i18n support, everything's just right!
A version bump, a new year to cheer,
LocaleSelector dances, spreading good cheer!
In the InlineDatePicker, joy will abound,
As rabbits rejoice in the changes we've found! 🌼

Tip

We have updated our review workflow to use the Anthropic's Claude family of models. Please share any feedback in the discussion post on our Discord.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 574f1cf and 5168f12.

Files selected for processing (4)

• pom.xml (1 hunks)
• src/main/java/com/flowingcode/addons/ycalendar/InlineDatePicker.java (3 hunks)
• src/main/resources/META-INF/frontend/fc-inline-date-picker/fc-inline-date-picker.js (2 hunks)
• src/test/java/com/flowingcode/addons/ycalendar/InlineDatePickerDemo.java (2 hunks)

Files skipped from review due to trivial changes (2)

• pom.xml
• src/main/resources/META-INF/frontend/fc-inline-date-picker/fc-inline-date-picker.js

Additional comments not posted (5)

src/test/java/com/flowingcode/addons/ycalendar/InlineDatePickerDemo.java (2)

5-5: LGTM!

The copyright year update is approved.

---

37-39: Verify the intended Vaadin version for the conditional check.

The addition of the conditional compilation block is approved as it enhances the flexibility of the component's internationalization capabilities.

However, please verify if the hardcoded Vaadin version check of 0 is the intended version to check against.

If the Vaadin version check is incorrect, update the condition to the intended version.

src/main/java/com/flowingcode/addons/ycalendar/InlineDatePicker.java (3)

5-5: LGTM!

The copyright year change is approved.

---

26-26: LGTM!

The new imports are approved.

Also applies to: 30-30, 32-32

---

78-86: LGTM!

The new setI18n method is approved for the following reasons:

• The method is correctly implemented and follows best practices by including a null check and using the JsonSerializer to set the i18n properties.
• The method is well-documented with a Javadoc comment.
• The method name and parameter name are clear and descriptive.