-
-
Notifications
You must be signed in to change notification settings - Fork 1k
feat(locale): update zh_CN location #3481
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
feat(locale): update zh_CN location #3481
Conversation
✅ Deploy Preview for fakerjs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #3481 +/- ##
==========================================
- Coverage 99.97% 99.97% -0.01%
==========================================
Files 2849 2856 +7
Lines 218992 219441 +449
Branches 952 949 -3
==========================================
+ Hits 218939 219386 +447
- Misses 53 55 +2
🚀 New features to boost your workflow:
|
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.
One last question from my side.
Could you also resolve the merge conflicts, please?
bca4236
Looks like every PR I submit modifies the
|
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.
Looks like every PR I submit modifies the
test/__snapshots__/locale-data.spec.ts.snap
file, so I have to resolve the conflicts one by one by following the steps below:
merge pr
=>sync fork
=>resolve confilcts
=>merge pr
=>sync fork
=>resolve confilcts
.....
Your assumption is correct. Thank you for your awareness.
I suggest that I'll be writing a comment asking you for conflict resolution in the PR which I'll take on next. This way you do not need to "blindly" resolve merge conflicts multiple times in all your PRs.
I also noticed that you removed "翠竹路" from the street names to trigger the workflow actions again. While this is really kind of you, it's not strictly necessary since the failing test is a flaky one we can simply rerun the failing tests. Do you want to add the removed street name again or are you fine without it being in the data set? Both options are fine for me. As soon as you answer (and take action if you desire to do so) I'll merge this PR for you.
That's great, thank you.
Got it. I think it's fine to just remove this data, since it's not that important. |
In that case I'll already merge this PR. It was previously approved so I'm dismissing the two approval rule this time. |
zh_CN location add
city_name
、continent
、country
、direction
、language
、secondary_address
、street_name
.