Planned Changes In Next Edition
We have a bunch of backward incompatible changes that we want to make when create our next edition. Currently we do not have edition support, so before we implement these changes we have to add edition support as well.
Remove classes
-- ftd.text: hello class: yo
Lang:
ftd
Looks better than
-- ftd.text: hello classes: yo
Lang:
ftd
Most of the time we want to add a single attribute. We use singular name for plural even for text style and css etc.
We can not removeclasses as it would break existing code, so we have to it on next edition.ftd.color
We should introduce
ftd.raw-color and change the definition of ftd.color to use ftd.raw-color instead of string as light and dark.ftd.image-src
We should also have
ftd.raw-image-src as the types of light and dark instead of string.fastn is fastn serve
ftd.device: string -> or-type
We currently use
string to represent ftd.device. Our or-type is superior and recommended way for modelling such enumerated constants.ftd.ui -> ui
Every other built in type has no prefix, so why does
ui? Also children, which is and alias for ftd.ui list does not have ftd. prefix.ftd.color-scheme related types
We have a few abbrevated names. We prefer longer/descriptive names.
ftd.btb -> ftd.body-text-borderftd.pst -> ftd.primary-secondary-tertiaryftd.custom -> ftd.custom-colors
Getting Help
Have a question or need help?
Visit our GitHub Q&A discussion to get answers and subscribe to it to stay tuned.
Join our Discord channel and share your thoughts, suggestion, question etc.
Connect with our community!Found an issue?
If you find some issue, please visit our GitHub issues to tell us about it.
Quick links:
Join us
We welcome you to join our Discord community today.
We are trying to create the language for human beings and we do not believe it would be possible without your support. We would love to hear from you.
Copyright © 2023 - FifthTry.com
