Skip to content
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

Fix plural with variables #29

Merged
merged 3 commits into from
May 3, 2016

Conversation

difelice
Copy link

@difelice difelice commented May 2, 2016

  • Fix Lint errors and warnings when running npm install
  • Fix plurals using variables not working

@coveralls
Copy link

coveralls commented May 2, 2016

Coverage Status

Coverage increased (+0.04%) to 89.516% when pulling 023e706 on difelice:fix-plural-with-variables into d124aa4 on i18next:master.

@coveralls
Copy link

coveralls commented May 2, 2016

Coverage Status

Coverage increased (+0.04%) to 89.516% when pulling 023e706 on difelice:fix-plural-with-variables into d124aa4 on i18next:master.

@cheton cheton merged commit caf57c9 into i18next:master May 3, 2016
@difelice
Copy link
Author

difelice commented May 3, 2016

Thank you!

@@ -246,7 +246,7 @@ class Parser {

props.forEach((prop) => {
if (_.includes(supportedOptions, prop.key.name)) {
options[prop.key.name] = prop.value.value;
options[prop.key.name] = prop.value.value || prop.value.name;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In case of other scenarios we didn't think of, how about changing it into this?

options[prop.key.name] = prop.value;

@cheton
Copy link
Member

cheton commented May 3, 2016

Thanks for your PR. I just made some minor changes with v1.2.1 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants