-
Notifications
You must be signed in to change notification settings - Fork 532
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(ts): make CSSClasses
types consistent
#4774
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 03a14f3:
|
co-authored-by: haroenv <haroenv@users.noreply.github.com>
f4178f2
to
7310de9
Compare
Yes, this make sense! |
c5edb61
to
b07301a
Compare
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.
I think this is good!
Summary
In some cases, we were exporting our
CSSClasses
types as required for our widgets, while they are in reality optional and partial.To avoid our users to provide extra logic over our types and to keep it consistent with our usage, the types are now:
Result
CSSClasses
type will be in the same file, namedFootComponentCSSClasses
Next step
templates
typesTicket
DX-1644