chore: Enable return of dependency CSS as Sass files #4044
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes it possible to extract the Sass files prior to compilation for the following CSS:
shinyDependencySassLayer()
selectizeSassLayer()
ionRangeSliderDependencySassLayer()
datePickerSassLayer()
The naming might look inconsistent, but there's a method: I added a new function adjacent to the
____CSS()
function for each component, replacingCSS
withSassLayer
.This is an internal-facing refactor to support dynamic theming in Shiny for Python, where we need access to the pre-compiled Sass files for each dependency.
Pairs with: