feat: add vaadin version as CSS classname

[javier-godoy]

Add a CSS classname derived from Vaadin version (demos-v24, demos-v25) for version-specific adjustments in add-ons demos.

Summary by CodeRabbit

• Chores
  • Enhanced demo component with version-based class name support, enabling version-specific styling capabilities for better compatibility across different Vaadin versions.

[coderabbitai]

Walkthrough

A single file modification that imports Vaadin's Version class and augments the demo component with a runtime CSS class name containing the major Vaadin version during router layout content display. No public API changes or control flow alterations beyond the new class name injection.

Changes

Cohort / File(s)	Summary
Version-based CSS class injection src/main/java/com/flowingcode/vaadin/addons/demo/TabbedDemo.java	Added Version import and runtime CSS class augmentation appending "demos-v" followed by major Vaadin version to the demo component's class list in showRouterLayoutContent method.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• feat: derive CSS classname from demo route #146: Modifies TabbedDemo.java's showRouterLayoutContent method to inject CSS class names onto the demo component using a similar pattern.

Suggested reviewers

• mlopezFC
• paodb

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding a Vaadin version as a CSS classname to the demo component, which matches the changeset modifications.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch vaadin-version-classname

---

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

[coderabbitai]

🧹 Nitpick comments (1)

src/main/java/com/flowingcode/vaadin/addons/demo/TabbedDemo.java (1)

215-215: Prefer setting the version class on the layout root once.

At Line 215 the class is added to each routed demo, which limits selectors to demo content and skips shared shell elements (tabs/footer). Consider adding it once to TabbedDemo instead.

♻️ Proposed refactor

@@ public TabbedDemo() {
-    setSizeFull();
+    addClassName("demos-v" + Version.getMajorVersion());
+    setSizeFull();
@@ public void showRouterLayoutContent(HasElement content) {
-    demo.addClassName("demos-v" + Version.getMajorVersion());

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/main/java/com/flowingcode/vaadin/addons/demo/TabbedDemo.java` at line
215, Currently each routed demo calls demo.addClassName("demos-v" +
Version.getMajorVersion()) which applies the version CSS class only to demo
content; move the responsibility to the layout root by adding this class once in
the TabbedDemo constructor (or initialization path) instead of per-demo, and
remove the demo.addClassName call from wherever demos are created; update code
that references demo.addClassName to use TabbedDemo (the root component) so
shared shell elements (tabs/footer) receive the version class.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@src/main/java/com/flowingcode/vaadin/addons/demo/TabbedDemo.java`:
- Line 215: Currently each routed demo calls demo.addClassName("demos-v" +
Version.getMajorVersion()) which applies the version CSS class only to demo
content; move the responsibility to the layout root by adding this class once in
the TabbedDemo constructor (or initialization path) instead of per-demo, and
remove the demo.addClassName call from wherever demos are created; update code
that references demo.addClassName to use TabbedDemo (the root component) so
shared shell elements (tabs/footer) receive the version class.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 827450a and 95ffa05.

📒 Files selected for processing (1)

• src/main/java/com/flowingcode/vaadin/addons/demo/TabbedDemo.java