Skip to content

Conversation

@mcollovati
Copy link
Collaborator

Fixes #22467

@mcollovati mcollovati added the target/25.0 Cherry-pick to 25.0 branch label Dec 22, 2025
@github-actions
Copy link

github-actions bot commented Dec 22, 2025

Test Results

1 311 files  ±0  1 311 suites  ±0   1h 14m 56s ⏱️ + 1m 46s
9 298 tests ±0  9 230 ✅ ±0  68 💤 ±0  0 ❌ ±0 
9 743 runs   - 9  9 667 ✅  - 9  76 💤 ±0  0 ❌ ±0 

Results for commit 34d9b01. ± Comparison against base commit 1567d4d.

♻️ This comment has been updated with latest results.


if (themeJson.lumoImports) {
const themeName = basename(themeFolder);
logger.warn(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was not able to observe this warning anywhere. Where should it show up? Should it be in the server logs instead?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to enable debug logs for dev server output tracker in dev mode (I don't remember the specific logger category right now)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this needs a logging configuration, then most likely this would never be seen by users, maybe it's better to place this warning in Java?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can probably be checked in ThemeValidationUtil

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the log message in TaskUpdateThemeImport

@mshabarov mshabarov changed the title fix: prevent lumo utility classes to be imported automatically fix!: prevent lumo utility classes to be imported automatically Dec 23, 2025
Copy link
Contributor

@mshabarov mshabarov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs better logging.

@mcollovati mcollovati requested a review from mshabarov December 23, 2025 11:23
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jan 9, 2026

@mshabarov mshabarov merged commit cda083a into main Jan 12, 2026
31 checks passed
@mshabarov mshabarov deleted the issues/22467-legacy_theme_dont_load_lumo_utilitites branch January 12, 2026 10:43
@vaadin-bot
Copy link
Collaborator

Hi @mcollovati and @mshabarov, when i performed cherry-pick to this commit to 25.0, i have encountered the following issue. Can you take a look and pick it manually?
Error Message:
Error: Command failed: git cherry-pick cda083a
error: could not apply cda083a... fix!: prevent lumo utility classes to be imported automatically (#23074)
hint: After resolving the conflicts, mark them with
hint: "git add/rm ", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

mcollovati added a commit that referenced this pull request Jan 12, 2026
caalador pushed a commit that referenced this pull request Jan 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Having a theme.json file present results in Lumo utilities being loaded (v25)

6 participants