-
Notifications
You must be signed in to change notification settings - Fork 18
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
fix: use the old icons importer for now [MDS-41] #234
Conversation
</#CodePreview> | ||
</:code> | ||
</ExampleAndCode> | ||
|
||
<ExampleAndCode id="currency_16" class="mt-4"> | ||
<:example> | ||
<IconJapaneseYen font_size="10rem" /> | ||
<Currency name="icon_japanese_yen" font_size="10rem" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good job! One note / question:
Currently Moon has agremeent, that Icons are named as separate components - so if some component goes missing, client has compile time error that needs to be fixed.
Does this approach has this validation?
Maybe you can propose some solution, that would have compile time check, that if logo/currency/icon is being used, but it does not exist, then instant feedback available. (Surface syntax has prop syntax key "values: [:list, :of, :supported, :values]" but maybe there is some alternative also?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 😁 Separate modules for icons are also generated. So they can also use that approach if compile time error detection is needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent! Very good!
Thank you! (heart)
No description provided.