-
-
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(name.findName): rename to fullName #1127
refactor(name.findName): rename to fullName #1127
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1127 +/- ##
=======================================
Coverage 99.64% 99.64%
=======================================
Files 2146 2146
Lines 230401 230432 +31
Branches 977 976 -1
=======================================
+ Hits 229585 229619 +34
+ Misses 795 792 -3
Partials 21 21
|
9924bdf
to
0af76ac
Compare
This is a none blocking/breaking change. So, can we merge this? |
Would this be merged anytime soon, as I am working on this module and I am afraid of conflicts? |
TBH, I don't see what's blocking the merge. Most likely just leaving this open in case anyone still wants a change. Often, many changes are merged in the release week. So I guess in one or two weeks. |
Lets just merge it then! No point to keep it hanging. @ST-DDT @Shinigami92 |
00f0d17
to
ce00b3f
Compare
This PR renames the existing
faker.name.findName()
tofaker.name.fullName()
, while keeping the existing function but marking them as deprecated.I also changed the signature of
fullName()
to an object for maintainability purposes.I had a discussion with @Shinigami92 last week about deprecations. We came to the conclusion that they should be categorized as
refactor
instead ofchore
, what I will start to implement with this PR.