bump version of @faker-js/faker used by plugin fakerTransform to latest version #3515
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
alex-vndly
approved these changes
Dec 2, 2022
Arhell
approved these changes
Dec 4, 2022
DavertMik
approved these changes
Feb 12, 2023
|
Thank you! Looks good 👍 |
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.
Motivation/Description of the PR
Bumping the version of @faker-js/faker used by plugin
fakerTransformto the latest version7.6.0. Staying current gives us access to expanded capabilities and access to nice api documentation.NOTE
I did not perform an exhaustive comparison of the 7.6.0 and 5.5.3 API. It is likely this will be a breaking change for folks using
fakerTransformpluginApplicable helpers:
Applicable plugins:
Type of change
Checklist:
npm run docs)npm run lint)npm test)