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

Ensure JSON keys match in language files, and fixes bug with fairnessImplementation Strings #101

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

CalvinRodo
Copy link
Contributor

No description provided.

@CalvinRodo
Copy link
Contributor Author

This should fail still requires keys to be fixed.

@CalvinRodo
Copy link
Contributor Author

Also please note as mentioned earlier this is failing intentionally right now to let us know what keys need to be fixed.

I'll continue to rebase this until it's been fixed.

@gcharest
Copy link
Member

👍 Not merging until you give me the ✔️

@CalvinRodo
Copy link
Contributor Author

for #96.

Well it'll be waiting on all the french text to be added before I can merge it,

@gcharest
Copy link
Member

What French terms are missing?

@CalvinRodo
Copy link
Contributor Author

Sorry just saw this now they get spit out during the test:
extra keys in en.json
proceduralFairnessImplementation1
proceduralFairnessImplementation2
proceduralFairnessImplementation3
proceduralFairnessImplementation4
proceduralFairnessImplementation5
proceduralFairnessImplementation6
proceduralFairnessImplementation7
proceduralFairnessImplementation8
proceduralFairnessImplementation9
proceduralFairnessImplementation10
proceduralFairnessImplementation11
proceduralFairnessImplementation12
proceduralFairnessImplementation13
proceduralFairnessImplementation14
proceduralFairnessImplementation15
proceduralFairnessImplementation16
proceduralFairnessImplementation17 extra keys in fr.json

Will probably have to rebase and run again.

@gcharest
Copy link
Member

gcharest commented Jun 18, 2019 via email

@CalvinRodo
Copy link
Contributor Author

@gcharest Any update on this do we need to add these questions in French or can we remove them from the English?

@gcharest
Copy link
Member

gcharest commented Aug 3, 2019

Yes, I'll review shortly. Was scheduled this morning but got sidetracked.

@CalvinRodo
Copy link
Contributor Author

Just a reminder to @gcharest or @MrDeshaies to validate the missing keys this test will be really useful for anyone adding new languages to the project since they'll be able to validate that the keys are matching.

@CalvinRodo
Copy link
Contributor Author

CalvinRodo commented Sep 22, 2019

Found the reason for the failure it was because of a bug in the coding of the fairnessImplementation strings

This PR fixes Bug #130

@CalvinRodo CalvinRodo changed the title I18n key test Ensure JSON keys match in language files, and fixes bug with fairnessImplementation Strings Sep 22, 2019
Added lodash
Added a test that fails if the number of keys in one language file doesn't match the number in the other.
Will spit out the extra keys if it fails.
@@ -55,6 +55,7 @@
"eslint-plugin-vue": "^5.0.0",
"jest-transform-stub": "^2.0.0",
"push-dir": "^0.4.1",
"lodash": "^4.17.11",
Copy link
Member

Choose a reason for hiding this comment

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

I forget how this package changed its deployment, but I think it might be better to install the individual components of lodash you're using instead of the full library. EX: lodash.isempty above in the dependencies

@CalvinRodo
Copy link
Contributor Author

CalvinRodo commented Oct 10, 2019 via email

@nschonni
Copy link
Member

Looks like https://www.npmjs.com/package/lodash.intersection and https://www.npmjs.com/package/lodash.difference
I think the separate ones are a good idea since lodash has had a view security issues recently that trigger the Security Alerts on GitHub. With the standalone packages, they're less likely to be affected unless it's actually related to that component

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

3 participants