-
-
Notifications
You must be signed in to change notification settings - Fork 943
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(locale)!: remove unused separator entry #1731
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## next #1731 +/- ##
=======================================
Coverage 99.64% 99.65%
=======================================
Files 2340 2340
Lines 242669 242653 -16
Branches 1111 1111
=======================================
- Hits 241819 241804 -15
+ Misses 829 828 -1
Partials 21 21
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a breaking change!
I'm not sure if this was used for But nowadays there is something like this: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/ListFormat |
It isn't supported there either. faker.helpers.fake("{{separator}}") [Error]: Invalid module method or definition: separator
- faker.separator is not a function
- faker.definitions.separator is not an array We don't use it and the only way to actually access it is via That's why I would like to remove it. |
I would like to discuss this in a meeting and want to raise the question if we need an alternative |
In today meeting we ensured that this entry was never used and can be removed savely. I would still suggest to mark this as breaking change. |
The
separator
is currently unused and doesn't really contain a separator, instead it contains a combinator:' & '
.This PR removes the separator from the definitions, the locale data and related scripts.
A following PR will move the
title
to a newmetadata
category to remove any exceptions from thelocale: { [category: string]: { [entry: string]: any }}
data structures. (To be able to remove the special case handling currently required for those fields).