Update web-component version to 1.4.0

[paodb]

Version 1.4.0 of the web-component adds support for styling menu container.

As the update on the web-component is an enhancement, version of the add-on was updated to 6.1.0-SNAPSHOT.

This PR also includes an update on the commons-demo dependency version.

Summary by CodeRabbit

• Chores
  • Bumped application version to 6.1.0-SNAPSHOT.
  • Updated AppLayout package to 1.4.0 for the embedded UI component.
  • Upgraded demo dependency to 4.2.0.
  • Adjusted development server rescan configuration for improved change detection.

[coderabbitai]

Walkthrough

The pull request updates project and dependency versions in pom.xml, replaces a Jetty plugin configuration element, and bumps the @NpmPackage version annotation in AppLayout.java. No methods or logic changes are introduced.

Changes

Cohort / File(s)	Summary of changes
Build and dependency configuration pom.xml	Project version updated 6.0.1-SNAPSHOT → 6.1.0-SNAPSHOT; property flowingcode.commons.demo.version 4.0.0 → 4.2.0; jetty-maven-plugin config: removed <scanIntervalSeconds>3</scanIntervalSeconds>, added <scan>3</scan>.
UI component annotation src/main/java/com/flowingcode/addons/applayout/AppLayout.java	@NpmPackage version updated 1.3.0 → 1.4.0; no code logic changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Update web-component version to 1.4.0" directly and concisely describes the primary change in the PR—upgrading the web component/AppLayout to v1.4.0—and includes the exact version number, making it clear for reviewers scanning history. It is specific, brief, and related to the changes in the diff.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch issue-24

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 59ede25 and 7a2748b.

📒 Files selected for processing (2)

• pom.xml (3 hunks)
• src/main/java/com/flowingcode/addons/applayout/AppLayout.java (1 hunks)

🧰 Additional context used

🧬 Code graph analysis (1)

src/main/java/com/flowingcode/addons/applayout/AppLayout.java (1)

src/test/java/com/flowingcode/addons/applayout/menu/PaperToggle.java (1)

• NpmPackage (27-30)

🔇 Additional comments (4)

src/main/java/com/flowingcode/addons/applayout/AppLayout.java (1)

46-46: LGTM! Version update aligns with web component release.

The NpmPackage version update from "1.3.0" to "1.4.0" correctly matches the web component release that adds support for styling the menu container.

pom.xml (3)

7-7: LGTM! Appropriate version bump for enhancement.

The project version bump from 6.0.1-SNAPSHOT to 6.1.0-SNAPSHOT follows semantic versioning correctly, as this is a minor version increment for an enhancement (web component update with new styling capabilities).

---

18-18: LGTM! Demo dependency updated.

The commons-demo version update from 4.0.0 to 4.2.0 appears to be a routine dependency update.

---

233-233: Verify the Jetty plugin configuration change.

The change from <scanIntervalSeconds>3</scanIntervalSeconds> to <scan>3</scan> appears to be a configuration update. Please verify this is the correct configuration for the Jetty Maven plugin version being used.
Based on the search results, I can see that both <scan> and <scanIntervalSeconds> have been used in different versions of the Jetty Maven plugin. Let me search for more specific information about Jetty version 11.0.14.Based on the search results, I can see there are different configuration element names used in different versions of the Jetty Maven plugin. Let me search specifically for the Jetty 11.x documentation to confirm the correct configuration element.The search results show that both scanIntervalSeconds and scan are used in different versions. Based on the official Jetty documentation for version 12, the configuration uses <scan> element. However, I noticed that in the search results, version 11 examples still show scanIntervalSeconds being used. Let me check one more time for version 11 specifically.Perfect! Now I have confirmation. The Jetty Maven plugin with the scan configuration set to a positive value performs complete application restart when the given number of seconds have elapsed since the last Java change. For instance: org.eclipse.jettyjetty-maven-plugin11.0.132

The change from <scanIntervalSeconds>3</scanIntervalSeconds> to <scan>3</scan> is correct for Jetty Maven plugin version 11.0.14. This aligns with the updated configuration format used in Jetty 11.x versions.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[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 SonarQube Cloud

[mlopezFC]

LGTM