-
-
Notifications
You must be signed in to change notification settings - Fork 919
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
refactor!: remove v8 deprecations #2608
Conversation
Uncommitted changes were detected after runnning |
For reference for the migration guide, these are the completely removed methods: (WIP, once this is finished we can add to the migration guide) Deprecated methods removedA large number of methods which were deprecated in v8 are completely removed in v9. To prepare for the upgrade, it is recommended to first upgrade to the latest version of v8 (e.g.
Changes to method signaturesMany methods that previously took multiple parameters now use a single parameter with an options object. For example //old
faker.commerce.price(100, 200, 0, '$')
//new
faker.commerce.price({min: 100, max: 200, dec: 0, symbol: '$'}
Other parameters renamed or removed
Old constructions for Faker removedSome old constructors for the Faker were removed. In most cases you should use one of the prebuilt Faker instances instead of the constructor, for example |
i think there might be logic in not removing the faker.phone.number({ format }) method in this initial commit until a good replacement (e.g. #2578 ) is merged? |
🤔 Mhh. I think having the alternative suggestions like the |
My initial draft for the migration guide is done, #2608 (comment) when you have a chance you can add that initial text to |
We might plan to split this PR into several smaller PRs. Like e.g. remove the image provider in one PR. |
Sure no hurry then |
Do you need/want help? |
Mh, mostly with the new I would like to potential go through the deprecation removals by module or/and by specific things (like image-providers and unique) At the end, try to do steps that are not get in conflict with each other 🙂 |
While I think there are a few special cases that need their own PRs like unique and the image providers, I think it's fine if most of the standard removals of deprecated methods is done in a single big PR. It's not too hard to review removals. |
2ef96fb
to
4c0fde9
Compare
c0d6187
to
922c55a
Compare
remove more
922c55a
to
a6c2263
Compare
This PR is too big and to confusing to review I will close this PR and we will do PRs for every module on its own |
Remove all v8 deprecations
we might need to split this PR into several smaller PRs, until this PR itself is small enough