fix(theme-classic): resolve customCss from site dir #7363
Merged
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.
Pre-flight checklist
Motivation
Because after #6921, relative paths from plugins are resolved relative to the plugin entry point, specifying relative CSS paths no longer works. (I don't know if it worked before; never tried. It's highly possible that it didn't either.) Anyways,
./src/css/custom.css
should definitely work.Test Plan
Used a relative path in our own config.