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 PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@razorpay/blade@11.13.0
Minor Changes
410cfb5: feat: add
circular
variant for theProgressBar
componentChanges
The
"meter"
&"progress"
values for thevariant
prop are deprecated in favor of the newtype?: "meter" | "progress"
prop.The
variant
prop now accepts"linear"
&"circular"
values.Usage:
Migration with Codemod
The codemod will automatically update the
ProgressBar
component. Execute the codemod on the file/directory that needs to be migrated for the page via the following command:npx jscodeshift ./PATH_TO_YOUR_DIR --extensions=tsx,ts,jsx,js -t ./node_modules/@razorpay/blade/codemods/migrate-progressbar/transformers/index.ts --ignore-pattern="**/node_modules/**"
There might be some situations where the codemod falls short, If you encounter errors, refer the following examples to migrate the component manually: