-
Notifications
You must be signed in to change notification settings - Fork 6
Nested objects are now allowed for translations. #6
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
Conversation
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 run ts lint: npm run tslint
and fix the errors
|
||
private filter(translations): any { | ||
for (let key in translations) { | ||
if (typeof translations[key] == "object" && translations[key] !== null && !Array.isArray(translations[key])) { |
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.
this line is too long
|
||
private filter(translations): any { | ||
for (let key in translations) { | ||
if (typeof translations[key] == "object" && translations[key] !== null && !Array.isArray(translations[key])) { |
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.
==
should be ===
It's another interesting approach but have you tried accessing them? because I think that But I like your tests (except the things tslint mentioned). |
@tflori yup, I'm fixing them now |
OK, I'm merging your logic and my tests together 😄 |
OK @tflori Everything is included now. Inclusive tests... Could you merge the PR and publish a new version? That would be charmin' 😄 |
Resolves #4