[default] fix: Use max to handle custom maximum value
#7142
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@th3f0r3ign3r is attempting to deploy a commit to the shadcn-pro Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes modifications to the
Progresscomponent in theapps/www/registry/default/ui/progress.tsxfile. The most important changes involve using themaxproperty on the component and updating the transformation style to use this property.Key changes:
maxproperty to theProgresscomponent to allow customization of the maximum value. (apps/www/registry/default/ui/progress.tsx)ProgressPrimitive.Indicatorto utilize the unusedmaxproperty, providing more flexibility in progress calculation. (apps/www/registry/default/ui/progress.tsx)