chore: add aura styles

[javier-godoy]

NOTE: There are a few lumo properties that seem to be unused.

The primary main var(--lumo-primary-color) is used, but Aura defaults looks fine.

[coderabbitai]

Walkthrough

This PR updates copyright years to 2026, renames a theme constant in the animated-fab React component, adds CSS variable fallbacks for improved compatibility, and introduces theme configuration support in the AppShellConfigurator Java class.

Changes

Cohort / File(s)	Summary
React Component Theme src/main/resources/META-INF/frontend/react/animated-fab.tsx	Renamed theme constant from lumoTheme to animatedFabTheme and updated ThemeProvider usage accordingly.
CSS Styling Updates src/main/resources/META-INF/frontend/styles/chat-assistant-styles.css, src/main/resources/META-INF/frontend/styles/chat-message-styles.css	Updated copyright years to 2026 and added CSS variable fallbacks (gap, padding, font-size, color) for improved compatibility with alternative variable namespaces.
Java Configuration src/test/java/com/flowingcode/vaadin/addons/AppShellConfiguratorImpl.java	Added public configurePage(AppShellSettings settings) method that checks and initializes dynamic theme support; updated copyright year to 2026.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Replace wc-chatbot with react and vaadin components #35: Renames and switches the theme constant used by the animated-fab React component, directly affecting the same file modified in this PR.

Suggested labels

enhancement

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

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.
Title check	❓ Inconclusive	The title claims to 'add aura styles', but the actual changes rename a theme constant, update CSS variable fallbacks, update copyright years, and add a configurePage method. Adding aura styles as fallbacks is only a minor part of the broader changes.	Consider a more descriptive title like 'Add Aura theme fallbacks and update copyright to 2026' to better reflect all changes in the PR.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch aura

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

src/main/resources/META-INF/frontend/react/animated-fab.tsx (1)

18-23: Consider adding fallbacks for light and dark warning palette entries too.

Lines 19 and 22 now have aura fallbacks for main and contrastText, but light (line 20) and dark (line 21) still reference --lumo-warning-color-50pct and --lumo-warning-color-20pct without fallbacks. If these Lumo variables are also undefined under the aura theme, the warning badge may not render correctly in hover/active states.

src/main/resources/META-INF/frontend/styles/chat-assistant-styles.css (1)

34-34: Consider adding a hardcoded final fallback value.

The other CSS file (chat-message-styles.css) uses a three-level fallback pattern ending in a hardcoded value (e.g., 0.25rem). Here, if neither --lumo-space-s nor --vaadin-gap-s is defined, the gap property would be invalid. A safe final fallback like 0.5rem could help:

gap: var(--lumo-space-s, var(--vaadin-gap-s, 0.5rem));

Tip

We've launched Issue Planner and it is currently in beta. Please try it out and share your feedback on Discord!

---

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