fix: prevent runtime error on malformed custom theme object #4375
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.
Changes:
Path
property of its metadata object is malformed,applyTheme.js
ends up callingcreateOrUpdateStyle
withundefined
as the first parameter.This failed silently before, as
cssText
could be a string only. After the recent CSP-related changes,cssText
can be either a string, or an object. To better reflect this change, thecssText
variable has been renamed tocssData
.Each error (of possible 3) is reported only once during custom theme detection
Most notably, when detecting a custom theme, each of the meta-classes is applied consecutively and tested for. This allows to test for
sapThemeMetaData-Base-baseLib
first, and only if not found, to look forsapThemeMetaData-UI5-sap-ui-core
. This preserves the old behavior.fixes: #4346