We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
When using warning custom containers, we write like this:
::: warning This is a warning :::
and when using warn(warning) Badge, we write like this:
<Badge text="beta" type="warn"/>
in custom containers is warning but in built-in component Badge is warn, why?
warning
warn
<!-- use warning rather than warn --> <Badge text="beta" type="warning"/>
use warning as a optional value in built-in component Badge rather than warn.
Badge
No.
The text was updated successfully, but these errors were encountered:
Actually warning value is already supported for the type property, but documentation is not up to date. I'll do an update.
type
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Feature request
What problem does this feature solve?
When using warning custom containers, we write like this:
and when using warn(warning) Badge, we write like this:
in custom containers is
warning
but in built-in component Badge iswarn
, why?What does the proposed API look like?
How should this be implemented in your opinion?
use
warning
as a optional value in built-in componentBadge
rather thanwarn
.Are you willing to work on this yourself?
No.
The text was updated successfully, but these errors were encountered: