-
-
Notifications
You must be signed in to change notification settings - Fork 860
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
Add linked message formatting #467
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #467 +/- ##
==========================================
+ Coverage 96.59% 96.64% +0.04%
==========================================
Files 9 9
Lines 647 655 +8
==========================================
+ Hits 625 633 +8
Misses 22 22
Continue to review full report at Codecov.
|
|
||
describe('linked translation', () => { |
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.
Note: Some describe('linked translation', () => {
lines are consolidated to single one.
I thinkt it is better to describe one concept that has several test cases.
Before
linked translation
✔️ should foo
linked translation
✔️ should bar
linked translation
✔️ should buz
After
linked translation
✔️ should foo
✔️ should bar
✔️ should buz
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.
Excellent work!
Addresses #106.
This PR allows linked keys accept formatting modifier in the form of
@.MODIFIER:key
.Supported modifiers are below.
upper
: Uppercase all the letters.lower:
: Uppercase all the letters.The suggested
camel
modifier is not implemented, since usuallythis Is Camel Case
are expected for camel-case.Instead of camel case, I think title-case such is useful, such as
The Catcher in the Rye
.Anyway, implementing camel-case and/or title-case is not trivial, so we should consifer using npm module such as to-title-case or similar.