-
-
Notifications
You must be signed in to change notification settings - Fork 949
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
chore: deprecate address.streetPrefix and suffix #1053
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1053 +/- ##
==========================================
- Coverage 99.62% 99.62% -0.01%
==========================================
Files 2153 2153
Lines 236493 236512 +19
Branches 976 975 -1
==========================================
+ Hits 235605 235621 +16
- Misses 867 870 +3
Partials 21 21
|
IMO either keep them as util functions (for custom tooling) or remove them completely, like don't advertise the usage with |
I do want to remove them, but I want to give everyone a chance to migrate. |
Nah, I think you misunderstood me. If we deprecate these functions, why leave the definitions? |
To give users a hint how they should structure their definitions to be compatible with our format/our existing locales. |
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.
IMO it is okay to remove / hide this from the end-user as I would not know what a street suffix/prefix would even be 🤷
We also didn't explain it anywhere but just provide it
In the end Faker should be a tool to generate meaningful data, and streetnames are totally okay, but what is a street prefix/suffix?
2930bdf
to
6b76c86
Compare
d6d86ff
to
d5e4332
Compare
The street prefix and suffix methods only generate parts of the data and not all of the locales support these.
IMO the methods aren't useful by themselves and thus should be removed.