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

Update i18n from Crowdin #2998

Merged
merged 566 commits into from
Nov 6, 2018
Merged

Update i18n from Crowdin #2998

merged 566 commits into from
Nov 6, 2018

Conversation

decabeza
Copy link
Collaborator

@decabeza decabeza commented Nov 2, 2018

References

This PR updates Crowdin changes with master branch including the PR from Crowdin bot: #2965 and changes made on #2974

Objectives

  • Update translations from Crowdin
  • Fix date translations
  • Fix language names
  • Merge master branch to resolve conflicts on .yml files

Consul Bot added 30 commits October 26, 2018 10:51
javierm and others added 22 commits November 5, 2018 18:20
We forgot to do it when we created the translation tables, and so now we
need to make sure we don't overwrite existing translations.
This way the task to migrate the data doesn't have to be run manually if
these migrations weren't already executed.
In theory, it should never happen, but that's why exceptions exist.
This way we can check everything is OK before actually migrating the
data to the translations tables.
We think aborting the migration will generate more headaches to system
administrators, who will have to manually check and fix every invalid
record before anything can be migrated.
Ruby can't have hyphens in method names, so sending something like
`record.title_pt-BR` would raise an exception.

Using globalize's `localized_attr_name_for` method fixes the bug.

Thanks Marko for the tip.
No developers are maintaining it anymore.
This way we can ask contributors to follow some basic guidelines like
removing trailing whitespaces while not overwhelming them with all our
rules.
As pointed out in PR consul#2734:

"After clicking the first link, there's an AJAX request which replaces
the existing `.in-favor a` and `.against a` links with new elements. So
if Capybara tries to click the existing `.against a` link at the same
moment it's being replaced, clicking the link won't generate a new
request".

Making Capybara check the page for new content before clicking the
second link solves the problem.

This commit solves issues afecting both Madrid's fork and the original
CONSUL repo.
We've agreed `User.new` is easier to read than `described_class.new` and
since we are ignoring Hound's comments regarding this topic, we might as
well remove it.
The content 'An example legislation process' is already present before
we click the "All" link.

Not checking the page content properly sometimes resulted in the second
click being executed before the first request had been completed, making
the spec fail.

By checking the "All" link isn't present anymore, we guarantee the
request has been completed before trying to click the 'An example
legislation process' link.
@voodoorai2000 voodoorai2000 merged commit e6f8814 into master Nov 6, 2018
@voodoorai2000 voodoorai2000 deleted the i18n-uptade-crowdin branch November 6, 2018 11:54
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

6 participants