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(manager): remove duplicate message #2002

Merged
merged 1 commit into from
May 1, 2024
Merged

fix(manager): remove duplicate message #2002

merged 1 commit into from
May 1, 2024

Conversation

sbruens
Copy link
Contributor

@sbruens sbruens commented May 1, 2024

This breaks the translation console pipeline, as it generates a message with the same ID but with different descriptions.

@sbruens sbruens requested a review from a team as a code owner May 1, 2024 19:50
@sbruens sbruens requested a review from daniellacosse May 1, 2024 19:50
@sbruens sbruens enabled auto-merge (squash) May 1, 2024 19:50
Copy link
Contributor

@jyyi1 jyyi1 left a comment

Choose a reason for hiding this comment

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

Do we also need to remove the corresponding entry in client/original_messages.json?

@sbruens
Copy link
Contributor Author

sbruens commented May 1, 2024

Do we also need to remove the corresponding entry in client/original_messages.json?

No. That's a different source file, so the message extractor is fine with that. I believe the source is used in the message ID generation.

Copy link
Contributor

@jyyi1 jyyi1 left a comment

Choose a reason for hiding this comment

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

LGTM as long as we don't want to distinguish different "other"s.

@sbruens sbruens merged commit 27f579f into master May 1, 2024
20 checks passed
@sbruens sbruens deleted the sbruens/fix-l10n branch May 1, 2024 20:03
@sbruens
Copy link
Contributor Author

sbruens commented May 1, 2024

LGTM as long as we don't want to distinguish different "other"s.

Yeah, if we'd need to do that we can use the meaning attribute, same as I did in #1934. In this case it seemed unnecessary since they have the same meaning (for an "Other" cloud provider in the old and new feedback forms).

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

Successfully merging this pull request may close these issues.

2 participants