feat: add cssStyler
option to use typed CSSStyleDeclaration props
#148
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.
deprecate
styler
in favor of a newcssStyler
which have better typing support and can use direct assignment. The previous use ofinnerHTML
made it easier to usestyler
but now that we switched to pure HTML Element, it is better to useCSSStyleDeclaration
props. Since we moved to pure HTML Element, thestyler
is requiring a bit more logic, since we now have to do string split of semicolon;
, then usetoCamelCase
for CSS assignment... which is why the newcssStyler
is better since we can simply loop through all styling props and assign directlyStyler (deprecated)
CssStyler (new)