You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried putting undefined for as a css attribute. It is accepted by the Typescript type. My expectation was that putting undefined on a css attribute would treat the property as if it was absent or never defined. Instead in the generated CSS, you take undefined and transform it into a string.
style({ paddingTop: undefined })
becomes: ._1ep1qzf0 { padding-top: undefined; }
Is there a reason why undefined it managed like this internally ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I tried putting undefined for as a css attribute. It is accepted by the Typescript type. My expectation was that putting undefined on a css attribute would treat the property as if it was absent or never defined. Instead in the generated CSS, you take undefined and transform it into a string.
style({ paddingTop: undefined })
becomes:
._1ep1qzf0 { padding-top: undefined; }
Is there a reason why undefined it managed like this internally ?
Beta Was this translation helpful? Give feedback.
All reactions