Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Translation] Fix message key handling for the Localise provider #42649

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

Closed
wants to merge 0 commits into from

Conversation

xepozz
Copy link
Contributor

@xepozz xepozz commented Aug 19, 2021

Q A
Branch? 5.3 and above
Bug fix? yes
New feature? no
Deprecations? no
Tickets Fix #...
License MIT
Doc PR -

Fixed non-recursively merging existing keys and created. Now created keys totally removed by usual merge.
Handled situation when no keys are created in localise service.

@xepozz xepozz changed the base branch from 5.4 to 5.3 August 19, 2021 15:35
@OskarStark
Copy link
Contributor

Thank you for the bugfix, can you please add a testcase to avoid further regressions?

cc @welcoMattic

@carsonbot carsonbot changed the title Fix localise provider [Translation] Fix localise provider Aug 20, 2021
@OskarStark OskarStark added this to the 5.3 milestone Aug 20, 2021
Copy link
Member

@welcoMattic welcoMattic left a comment

Choose a reason for hiding this comment

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

It miss tests, but for me it looks good

@xepozz
Copy link
Contributor Author

xepozz commented Aug 21, 2021

Done

@OskarStark
Copy link
Contributor

@welcoMattic can you please review/test again? Thanks

@derrabus
Copy link
Member

Since the PR title will appear in the ChangeLog of the next release: Can we please find a better one? The current title does not tell me what aspect of the provider needs fixing.

@xepozz
Copy link
Contributor Author

xepozz commented Aug 23, 2021

How can I help you?
I really need this fix. Can we speed up please?

@fabpot fabpot changed the title [Translation] Fix localise provider [Translation] Fix message key handling for the Localise provider Aug 23, 2021
@fabpot
Copy link
Member

fabpot commented Aug 23, 2021

Thank you @xepozz.

fabpot added a commit that referenced this pull request Aug 23, 2021
…ovider (xepozz)

This PR was squashed before being merged into the 5.3 branch.

Discussion
----------

[Translation] Fix message key handling for the Localise provider

| Q             | A
| ------------- | ---
| Branch?       | 5.3 and above
| Bug fix?      | yes
| New feature?  |no <!-- please update src/**/CHANGELOG.md files -->
| Deprecations? |no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tickets       | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License       | MIT
| Doc PR        | -

Fixed non-recursively merging existing keys and created. Now created keys totally removed by usual merge.
Handled situation when no keys are created in localise service.

Commits
-------

36b4837 [Translation] Fix message key handling for the Localise provider
@fabpot fabpot closed this Aug 23, 2021
@fabpot fabpot force-pushed the fix-localise-provider branch from aee469a to 36b4837 Compare August 23, 2021 09:24
@xepozz xepozz deleted the fix-localise-provider branch August 23, 2021 17:51
@fabpot fabpot mentioned this pull request Aug 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants