bugFix resolving type mismatch w.r.t DescriptorType #4463
Merged
+122
−31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stschr
force-pushed
the
dolby/descriptorType_bugfix
branch
from
02e6d28
to
6a90f96
Compare
dsilhavy
approved these changes
Apr 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
resolving #4461
Since DASH schema defines
@valueasxs:string, I strictly cast any incoming values to String as well. (i.e, avoiding dynamic typing withinDescriptorTypeclass), but also apply the cast prior to theString.match()method ininArray()method to increase robustness for cases where the value member get updated afterinit().Additionally, I added unit tests for
inArray()method.