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
This seems to be working really well, but only for a very limited set of properties. Is there anything that needs to be done besides adding the remaining CSS data types and completing the Style enum? For example, is there any chance to make the 1"em" thing look less awkward? Thanks!
The text was updated successfully, but these errors were encountered:
The 1"em" problem is that as soon as the lexer sees an e after a number, it thinks it's shorthand for a float in standard form e.g. 1.34e32. See this feature request.
Otherwise it's just a case of implementing all the properties. I was implementing them as I needed them. I think I've handled a lot of the more fiddly ones, but yeah it's not complete yet. There is also the issue of other properties not covered by my selection strategy (candidate recommendation and above), and also the inherit et. al. property values. And finally there is the issue of deciding exactly how they render. I want to support
Where the properties are all static, render ahead-of-time into a static string.
Into a string on the heap at runtime
Into a string in a bump arena, so it works well with dodrio
Into the AST, so that styles can be handled however the crate user wants.
I still need to support all these cases. This also means that I need an easy way for the user to create property values (and possibly whole properties) with a macro. I've started this work, but there's a lot to do.
This seems to be working really well, but only for a very limited set of properties. Is there anything that needs to be done besides adding the remaining CSS data types and completing the
Style
enum? For example, is there any chance to make the1"em"
thing look less awkward? Thanks!The text was updated successfully, but these errors were encountered: