-
Notifications
You must be signed in to change notification settings - Fork 168
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
Applying an application theme with global styles #9246
Comments
@pleku is this planned to be backported to v14? |
@knoobie yes it is. But as the target release is v19 beginning of March, I would not expect this to v14 before early Q2 2021 🙍♂️ |
@pleku thanks for the info! I'm really looking forward to this. Q2+ is totally fine for more. |
Great to hear, since to be honest, I feel really bad about having to say it takes almost 6 months to get the value to the users. 😅 |
@pleku You don't have to. Quality gates and proper development take time. It's not like the feature is already done. You are currently developing it. Just as example: Spring Boot changed to a 6 month release circle of the upcoming 2.x releases as well. Meaning they now "publish" / "plan" the stuff that is coming in Q2 2021 like you do with theming. |
To be released in 6.0.0.alpha1 |
When building an app, I want to apply a theme to the app from one location in the project which will automatically inject the defined css there as global styles, so that I don't have to do it myself
The theme folder is inside the project in
frontend/theme/mytheme/
and applied with@Theme("mytheme")
annotation. This means the annotationvalue
attribute is changed to typeString
and the current value, an attribute of typeClass
, is renamed tobaseTheme
. Usage of both at the same time should throw an exception describing that it is not supported and only one should be used. Also thevariant
attribute is only relevant when thebaseTheme
is used.Applying the
@Theme
annotation on a class implementing@AppShellConfigurator
will take the theme into use. Discovering multiple theme annotations on the classpath should throw, as it used to be so that the theme was defined in the root layout and user might accidentally forget to remove that.The webpack build will get the used theme and then load any css from there as global css. Depends on #9245.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: