-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-add Object/toString CSSColor implementation #31
Comments
Right I caught an infinite loop while migrating this part to ClojureScript. It's not strictly needed for ClojureScript compatibility but just commented it waiting for a better solution. Have you tried something like |
Oh, wrapping with another vector suppresses commas? Very useful, I should pay more attention. I won't mind if you close this issue, but if you are looking to reinstate a toString we could keep it open. |
I'll let @noprompt comment on that, I personnaly don't really have an opinion :) |
Yes |
This patch rethinks the architecture of Garden in terms of well defined boundaries between parsing and compiling. Instead of directly compiling objects into CSS, Garden will first parse the objects into a CSS AST which can then be consumed by the compiler. This architecture is closer to what one might expect to find in a programming language implementation setting. This new architecture yields greater flexibility to introduce new features and semantics while vastly simplifying the work of the compiler. As a result many requested features and solutions to bugs have now been either implemented, solved, or are now trivial to implement or solve. Changelog updates forthcoming. Closes #31 Closes #109 Closes #115 Closes #116 Closes #119 Closes #120 Closes #121
Continued from: eb16db6#commitcomment-4614132
Commit eb16db6 included the following hunk:
This was presumably done in the interest of ClojureScript compatibility, however, the implicit
as-hex
string conversion of CSSColor instances is very convenient:In the interests of bringing back this feature I propose either:
(as-hex this)
in a try catch and return a default string.This is not a major issue, of course, but it would be nice.
Thanks!
The text was updated successfully, but these errors were encountered: