Fix UnknownProperty being used for known properties #152
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.
If the parser options
IncludeUnknownDeclarations
orAllowInvalidValues
are set totrue
,StylesheetComposer
will incorrectly useUnknownProperty
for everything, even when the property name in question is a known one.Fixed by first trying to create the property with the specified name and only falling back to
UnknownProperty
if the created property is null and one ofIncludeUnknownDeclarations
orAllowInvalidValues
are set.The new test case is an example of something that was failing without this fix - despite
border-width
being a known property name, the parsed output would have this as anUnknownProperty
in the child list.