Fix javadoc warnings

[paodb]

Close #8 & #10

Summary by CodeRabbit

• New Features

  • Enhanced documentation standards for Javadoc generation, ensuring stricter compliance with warnings.
  • Improved parameter naming for better clarity in method signatures of the DayOfWeekSelector class.

• Bug Fixes

  • Removed misleading return type documentation from the setWeekDaysShort method.

• Chores

  • Updated Maven configuration for GPG signing to activate only with a provided passphrase.

[coderabbitai]

Walkthrough

The changes in this pull request focus on modifications to the pom.xml file and the DayOfWeekSelector class. The pom.xml updates include enabling stricter Javadoc warning handling by setting failOnWarnings to true and enhancing the GPG profile activation condition. In the DayOfWeekSelector class, documentation comments for two methods have been refined, correcting Javadoc warnings related to return types and parameter names, while the method functionality remains unchanged.

Changes

File	Change Summary
pom.xml	Updated failOnWarnings to true in maven-javadoc-plugin and enhanced GPG profile activation.
src/main/java/com/flowingcode/vaadin/addons/dayofweekselector/DayOfWeekSelector.java	Removed return type documentation from setWeekDaysShort and changed parameter name in setFirstDayOfWeek.

Assessment against linked issues

Objective	Addressed	Explanation
Fix Javadoc warnings (Issue #8)	✅
Fix Javadoc warnings (Issue #8)	✅

Possibly related PRs

• build: upgrade javadoc plugin to 3.11.1 #9: The changes in this PR also involve modifications to the pom.xml file, specifically related to the maven-javadoc-plugin, including the failOnWarnings property, which connects directly to the changes made in the main PR.

Suggested reviewers

• mlopezFC

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

src/main/java/com/flowingcode/vaadin/addons/dayofweekselector/DayOfWeekSelector.java (1)

208-213: Consider enhancing the parameter documentation.

While the parameter name is now correct, consider improving the documentation:

1. The description could better explain that this parameter sets which day should appear first in the selector
2. The @throws clause should specify the invalid values that trigger the exception

Consider updating to:

   /**
    * Sets the first day of the week.
    * <p>
    * 0 for Sunday, 1 for Monday, 2 for Tuesday, 3 for Wednesday, 4 for Thursday, 5 for Friday, 6 for
    * Saturday.
    *
-   * @param first the index of the first day of the week
-   * @throws IllegalArgumentException if firstDayOfWeek is invalid
+   * @param first the day that should appear first in the selector
+   * @throws IllegalArgumentException if the provided DayOfWeek is null
    */

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8455db2 and e032a5a.

📒 Files selected for processing (2)

• pom.xml (1 hunks)
• src/main/java/com/flowingcode/vaadin/addons/dayofweekselector/DayOfWeekSelector.java (1 hunks)

🔇 Additional comments (3)

src/main/java/com/flowingcode/vaadin/addons/dayofweekselector/DayOfWeekSelector.java (2)

211-211: LGTM! Parameter name now matches the method signature.

The Javadoc parameter name has been correctly updated to match the method signature, fixing the warning.

---

Line range hint 182-193: LGTM! Removed incorrect @return tag.

The documentation is now correct for this void method, fixing the Javadoc warning.

pom.xml (1)

308-308: LGTM! Setting failOnWarnings to true enforces better documentation quality.

This change aligns with the PR objectives to fix Javadoc warnings by making the build fail when warnings are present. This is a good practice that helps maintain high-quality documentation.

[mlopezFC]

LGTM