-
Notifications
You must be signed in to change notification settings - Fork 185
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
Short names #318
Short names #318
Conversation
a72cc19
to
7595576
Compare
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
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.
The package names for the data provider crates are long. We should consider taking this opportunity to shorten them as well. My suggestion:
- icu_testdata (status quo)
- icu_data (replaces icu_data_provider)
- icu_data_cldr (replaces icu_cldr_json_data_provider)
- icu_data_fs (replaces (icu_fs_data_provider)
@@ -1,5 +1,5 @@ | |||
[package] | |||
name = "icu-cldr-json-data-provider" | |||
name = "icu_cldr_json_data_provider" |
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.
Hmm. "icu_data_cldr"
?
@@ -1,5 +1,5 @@ | |||
[package] | |||
name = "icu-data-provider" | |||
name = "icu_data_provider" |
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.
Maybe just "icu_data"
, and then the class is called DataProvider?
I'd rather go for |
7595576
to
c11227b
Compare
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Is there a way we could have the renames happen after 0.1 is tagged?
Unless you think renames are critical -- as they well may be, since after
0.1 sweeping renames would probably be harder.
I will say that I'm not exactly looking forward to merging that with my
upcoming changes, but I understand if it is necessary. :)
…On Fri, Oct 9, 2020 at 1:19 PM jira-pull-request-webhook[bot] < ***@***.***> wrote:
Notice: the branch changed across the force-push!
- components/datetime/benches/datetime.rs is no longer changed in the
branch
- components/datetime/benches/fixtures/tests/styles.json is no longer
changed in the branch
- components/datetime/examples/work_log.rs is no longer changed in the
branch
- components/datetime/tests/datetime.rs is no longer changed in the
branch
- ***@***.***/en.json
is no longer changed in the branch
- ***@***.***/pl.json
is no longer changed in the branch
- components/datetime/tests/fixtures/data/icu4x/dates/manifest.json is
no longer changed in the branch
- components/datetime/tests/fixtures/data/icu4x/manifest.json is no
longer changed in the branch
- components/datetime/tests/fixtures/tests/styles.json is no longer
changed in the branch
- components/fs_data_provider/tests/test_file_io.rs is different
- components/fs-data-provider/tests/testdata/json_plurals_37/manifest.json
is no longer changed in the branch
-
***@***.***/ar.json
is no longer changed in the branch
-
***@***.***/de.json
is no longer changed in the branch
-
***@***.***/en.json
is no longer changed in the branch
-
***@***.***/iw.json
is no longer changed in the branch
-
***@***.***/sr.json
is no longer changed in the branch
-
***@***.***/und.json
is no longer changed in the branch
-
***@***.***/zh.json
is no longer changed in the branch
-
***@***.***/ar.json
is no longer changed in the branch
-
***@***.***/en.json
is no longer changed in the branch
-
***@***.***/es.json
is no longer changed in the branch
-
***@***.***/he.json
is no longer changed in the branch
-
***@***.***/sr.json
is no longer changed in the branch
-
***@***.***/und.json
is no longer changed in the branch
-
***@***.***/yue.json
is no longer changed in the branch
- components/pluralrules/benches/fixtures/plurals.json is no longer
changed in the branch
- components/pluralrules/tests/data/json_plurals_37/manifest.json is
no longer changed in the branch
- ***@***.***/ar.json
is no longer changed in the branch
- ***@***.***/cs.json
is no longer changed in the branch
- ***@***.***/de.json
is no longer changed in the branch
- ***@***.***/en.json
is no longer changed in the branch
- ***@***.***/es.json
is no longer changed in the branch
- ***@***.***/fr.json
is no longer changed in the branch
- ***@***.***/it.json
is no longer changed in the branch
- ***@***.***/pl.json
is no longer changed in the branch
- ***@***.***/sk.json
is no longer changed in the branch
- ***@***.***/uk.json
is no longer changed in the branch
- ***@***.***/zh.json
is no longer changed in the branch
- ***@***.***/ar.json
is no longer changed in the branch
- ***@***.***/cs.json
is no longer changed in the branch
- ***@***.***/de.json
is no longer changed in the branch
- ***@***.***/en.json
is no longer changed in the branch
- ***@***.***/es.json
is no longer changed in the branch
- ***@***.***/fr.json
is no longer changed in the branch
- ***@***.***/it.json
is no longer changed in the branch
- ***@***.***/pl.json
is no longer changed in the branch
- ***@***.***/sk.json
is no longer changed in the branch
- ***@***.***/uk.json
is no longer changed in the branch
- ***@***.***/zh.json
is no longer changed in the branch
- components/pluralrules/tests/plurals.rs is no longer changed in the
branch
View Diff Across Force-Push
<https://github.com/unicode-org/icu4x/compare/unicode-org:7595576..unicode-org:c11227b>
~ Your Friendly Jira-GitHub PR Checker Bot
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#318 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB4GMFXRGZ7U2QKXX2FU4DSJ5V3TANCNFSM4SKOJF4A>
.
|
icu_provider works for me. If we want to reduce disruptions to merging, we could start by renaming the packages and modules but keeping the file system paths the same. |
@zbraniecki says he'll revisit this PR next week, so @filmil you are unblocked. |
I'm going to recreate a new PR based on the outcome of #304. |
Fixes #304.
Depends on #311