-
Notifications
You must be signed in to change notification settings - Fork 187
fix: move CSS imports from @Theme to bootstrap JS file #22518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Test Results1 256 files - 19 1 256 suites - 19 1h 19m 36s ⏱️ + 1m 10s For more details on these failures, see this check. Results for commit d8bfa48. ± Comparison against base commit d80a896. This pull request removes 128 and adds 1 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
entryPoint.getModulesDevelopmentOnly() | ||
.addAll(classInfo.modulesDevelopmentOnly); | ||
if (classInfo.loadCss) { | ||
if (classInfo.loadCss || activeTheme |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the loadCss is always false for all theme files and activeTheme now lets through all theme files even with loadCss false. So the flag can be fully removed.
Assert.assertEquals( | ||
"Project contains 4 css injections to document and all should be hashed", | ||
4l, getCommandExecutor().executeScript( | ||
"Project contains 2 css injections to document and all should be hashed", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What global css has embedded applications lost?
|
||
protected <T> List<String> merge(Map<T, List<String>> css) { | ||
protected <T> List<String> merge(Map<T, List<String>> outputFiles) { | ||
// Ignore app shell imports and definitions for bundle build detection, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't app shell imports also be taken into account by flow as they are not added to the general imports anymore even though they were there before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart from unit tests, the feature that is affected here is the bundle build.
Should the bundle include theme CSS imports? I don't know, but the current implementation didn't. So I assumed that my changes at some point produced a valid failure in the bundle ITs because of including CSS imports again. Ignoring here addresses this failure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mshabarov what was the css state for bunldes.
From what I see in tests and code I would expect css to be bundles and Theme css especially
|
Fixes #22517