You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding a packaged theme shouldn't require a new dev bundle generation until the packaged theme defines any external assets to be added to the project (assets block in theme.json).
Possible implementation details:
Flow needs to look at the frontend/generated/jar-resources/themes at build time and add the link tag to reference the styles.css on the page for each packaged theme.
Static file server should serve the CSS and assets defined in the packaged theme from frontend/generated/jar-resources/themes/my-packaged-theme.
Flow should spot an external assets included into packaged theme and trigger a new bundle generated to serve these assets from applicaiton bundle during the next runs.
The text was updated successfully, but these errors were encountered:
Serves styles and assets also for the packaged custom theme available from frontend/generated/jar-resources/themes
Calculates the hash of the theme.json for the packaged theme and records it to the bundle's stats.json
Checks if the hashes from the packaged themes match the corresponding hashes in the stats.json
Rebuilds the bundle if the packaged themes are added/updated (hashes don't match).
Fixes#15691
Custom themes packaged as a
JAR
dependency (parent theme and re-used theme) should work in Express Build mode.Acceptance criteria:
assets
block intheme.json
).Possible implementation details:
frontend/generated/jar-resources/themes
at build time and add the link tag to reference thestyles.css
on the page for each packaged theme.frontend/generated/jar-resources/themes/my-packaged-theme
.The text was updated successfully, but these errors were encountered: