-
-
Notifications
You must be signed in to change notification settings - Fork 861
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 pluralization feature to directive #304
Conversation
btw I think this will fail 3 unit tests however those same three tests failed in the fork I took, ie. those tests are not related to the scope of this PR. |
Codecov Report
@@ Coverage Diff @@
## dev #304 +/- ##
==========================================
+ Coverage 96.11% 96.12% +0.01%
==========================================
Files 9 9
Lines 617 620 +3
==========================================
+ Hits 593 596 +3
Misses 24 24
Continue to review full report at Codecov.
|
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.
Thanks!
Could you revert dist/*.js
please?
I build these files when vue-i18n release.
OK done |
Thanks! |
Yeah I did that already |
package-lock.json
Outdated
@@ -1,19 +1,9 @@ | |||
{ | |||
"name": "vue-i18n", | |||
"version": "7.4.2", |
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.
Please revert package-lock.json changing. 🙏
… by @SirLamer * Add "choice" quantity support to v-t directive * Add unit tests * Revert dist changes
This adds pluralization support to the v-t direction using the additional property "choice". The implementation is slightly sloppy but lightweight in that it makes use of the existing division between $t and $tc. The main reason I wanted this was to take advantage of the performance optimization opportunity afforded by the directive use case.
I have included unit tests but I have not updated the documentation since I am not certain of your workflow structure you're using for docs.
Sorry I committed the dist file before seeing that your contributing guidelines ask that it not be committed, as a tip for the future I suggest you add the dist folder to .gitignore and have GitHub compile the dist folder for you. In this case you'll probably have to merge the PR and then run a recompile and merge that in to capture any other changes since my fork on March 4th.