-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Types(severity): Inconsistency #4169
Comments
It is also possible to agree one of |
I suggested the same thing with a PR: #4040 |
That's what I was offering. I'm happy to be on the same page with you. Thanks! |
Similar to #5404 |
@mertsincan We should have a look at this case for next release I think. |
I have made everything consistent and updated the TS defs and Tailwind styles now just need to update the theme CSS.
|
Describe the feature you would like to see added
Hi,
Currently we are having
severity
in 7 different places. Instead of havingseverity
prop's possible values in 7 different places, can we make it in global and import from global types file? I am asking this because, as you can see below in some places we are definingwarn
, in some places we are definingwarning
. IMO it is inconsistent and it is better to have unified version of severities in some place. If you wish we can also Omit not necessary possible values while referring global severity type. WDYT?Is your feature request related to a problem?
No response
Describe the solution you'd like
No response
Describe alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: