fix: add subdirectory deployment support for brandSpinnerUrl #37523
+3
−0
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.
SUMMARY
This PR fixes theme token handling for subdirectory deployments by ensuring
brandSpinnerUrlgets properly prefixed with the application root path, similar to howbrandLogoUrlandAPP_ICONare already handled.Problem
When Superset is deployed under a subdirectory (e.g.,
/superset/,/analytics/), the loading spinner image (brandSpinnerUrl) would break because its URL wasn't being prefixed with the application root. This caused 404 errors for the spinner image in non-root deployments.Root Cause
The application initialization code already handled
brandLogoUrlandAPP_ICONfor subdirectory deployments, but missedbrandSpinnerUrl, which is another theme token that references static assets.Solution
Extend the existing subdirectory handling logic to include
brandSpinnerUrltoken, applying the same pattern used forbrandLogoUrl.TESTING INSTRUCTIONS
ADDITIONAL INFORMATION