Strict mode and review CSS Types #206
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.
Taking over from #116
This PR adds a strict mode feature, originally proposed by @fgnass
Strict mode is
false
by default.I also did a review of the CSS Types, which closes #48. For example, this allows numbers in
margin
properties, since internally we convert them topx
.Important note
When
strict: true
shorthands have a stricter syntax:AFAIK its not possible to type strings that can contain multiple values.
Unless, somehow, we create all the possible combinations of all tokens? (sounds like a terrible, terrible idea)
Say you have 4 space tokens: $1, $2, $3, $4
And you wanna add margin on all sides, you can do:
margin: "$2" // this passes validation, because its a single value in a string and its a token
Now you wanna set margin top/bottom and margin left/right
margin: "$2 $4" // As far as TS is concerned, this is still a single string so it cant offer you autocomplete
The only way would be to construct all the possible strings: