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(events): Fix wrong wording for commented on pull request #262

Merged
merged 1 commit into from
Aug 16, 2017
Merged

fix(events): Fix wrong wording for commented on pull request #262

merged 1 commit into from
Aug 16, 2017

Conversation

machour
Copy link
Member

@machour machour commented Aug 16, 2017

Closes #261

@lex111
Copy link
Member

lex111 commented Aug 16, 2017

Hmm, for sure, here is a similar situation as the IssueCommentEvent.

@machour do you think it can then refactor the code of this event, as it is done in IssueCommentEvent, or is it superfluous?

@machour
Copy link
Member Author

machour commented Aug 16, 2017

I didn't see that wording yet, so I'm not sure. But I think it's superfluous for now, as I don't think the current translation system is okay in general.

I'll open a new ticket with all my thoughts on the subject and a much cleaner implementation proposal where en.js wouldn't be needed anymore, and translators wouldn't have to struggle with words as some translations are used in different places with different meanings.

@lex111
Copy link
Member

lex111 commented Aug 16, 2017

Specifically about these cases - this is an exception, if GitHub returned the correct action, would not have to do a substitution.

It would be interesting to know about the cleaner implementation, well, let's discuss this in the new issue.

@@ -155,7 +155,7 @@ class Events extends Component {
'auth.events.pullRequestReviewCommentEvent',
language,
{
action: translate(`auth.events.actions.${action}`, language),
action: translate('auth.events.actions.commented', language),
Copy link
Member

Choose a reason for hiding this comment

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

I'm assuming it's incorrect because passing in created is why the wrong message shows right? Perfectly okay with having .commented specifically here in that case

@housseindjirdeh
Copy link
Member

Thanks for this homie 👍

@housseindjirdeh housseindjirdeh merged commit 182bc11 into gitpoint:master Aug 16, 2017
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.

3 participants