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
views/comments i18n #15059
views/comments i18n #15059
Conversation
|
Thank you for opening this PR! We appreciate you! For all pull requests coming from third-party forks we will need to A Forem Team member will review this contribution and get back to |
|
Hey @yheuhtozr! 👋 Can you please update your branch with the latest code from the repository’s |
036d36f
to
6e8547e
Compare
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.
Approving pending the merge conflict resolution.
|
@citizen428 Do you perhaps mean pending conflicts resolved by me? If so, it says "conflicts are too complex to resolve in the web editor" and I don't commit to my GitHub repo directly. |
Yes, I did. 😅
I'm not sure I understand. |
6e8547e
to
1b09775
Compare
1b09775
to
eb7f981
Compare
eb7f981
to
15b74fa
Compare
|
@citizen428 My GitHub repo is just a mirror of GitLab. I tried to sync with the main branch but GitHub does not recognize it as resolution and still showing conflicts. Even though I can solve it here, it will be reverted at the next time I push anything to my GitLab repo. Hopefully now the conflicts are simple - you only have to accept all my changes, so if you don't mind, please resolve them immediately before you merge this PR. BTW the reconciliation commit is rather big that you might want to check it again. |
3cda498
to
15b74fa
Compare
|
@yheuhtozr The spec errors here look legit, maybe something went wrong during the merge? |
|
@citizen428 The template went through a rather complex rewrite that I can't pin down the error source for now. It might need a repush, so you can look for other PRs ready to merge if you don't mind. |
|
Thanks for letting me know @yheuhtozr! |
|
@citizen428 The last error Travis reports is two missing keys, but it doesn't miss anything on my local environment. Could you let me know which ones specifically? |
|
@yheuhtozr Sure, the |
|
@citizen428 Now it fails with a mysterious error in a newly added(?) test, which doesn't look relevant to my changes? |
|
@yheuhtozr Looking into it. |
Co-authored-by: Michael Kohl <citizen428@forem.com>
|
@yheuhtozr Re-ran the specs, they are green now. |
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.
Thanks for taking on these changes! I noticed just a couple of small issues, but otherwise all looking great 🔥
| <li class="mod-actions hidden mod-actions-comment-button" data-path="<%= URL.comment(comment) %>/mod" aria-label="Moderate <%= comment.user.name %>'s comment"></li> | ||
| <li class="report-abuse-link-wrapper" data-path="/report-abuse?url=<%= URL.comment(comment) %>" aria-label="Report <%= comment.user.name %>'s comment as abusive or violating our code of conduct and/or terms and conditions"></li> | ||
| <li class="mod-actions hidden mod-actions-comment-button" data-path="<%= URL.comment(comment) %>/mod" aria-label="<%= t("views.comments.menu.moderate.aria_label", user: comment.user.name) %>"></li> | ||
| <li class="report-abuse-link-wrapper" data-path="/report-abuse?url=<%= URL.comment(comment) %>" aria-label="<%= t("views.comments.menu.report.aria_label", user: comment.user.name) %>"></li> |
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.
(not blocking at all) Nice one adding the aria-label translations here - it's also made me notice that the labels aren't actually being attached to the inner buttons/links, only to the list item, so they're not having the desired effect.
This is still great though, and sets us up well to fix that in a later issue as it's nothing to do with your changes. Just wanted to say yay for bringing it to our attention!
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.
Thanks for making that small fix!
* views/comments etc i18n * comments PR fixes * PR sync with main * remove ja.yml * Update _comment_header.html.erb * Update index.html.erb * Update _comment_header.html.erb * Update en.yml * Update fr.yml * Update config/locales/views/comments/en.yml Co-authored-by: Michael Kohl <citizen428@forem.com> * Update _comment_date.erb * Update en.yml * Update fr.yml Co-authored-by: Michael Kohl <citizen428@forem.com>
What type of PR is this? (check all applicable)
Description
Extracts strings for i18n from app/views/comments and related. Attached fr locale for testing purposes. Existing translations up to #15002 reflected (hopefully).
Related Tickets & Documents
Relates to #14888
QA Instructions, Screenshots, Recordings
UI accessibility concerns?
Added/updated tests?
have not been included
[Forem core team only] How will this change be communicated?
Will this PR introduce a change that impacts Forem members or creators, the
development process, or any of our internal teams? If so, please note how you
will share this change with the people who need to know about it.
Storybook (for Crayons components)
updated. I have filled out the
Changes Requested
issue template so Community Success can help update the Admin Docs
appropriately.
CHANGELOG.mdor in a forem.dev post
[optional] Are there any post deployment tasks we need to perform?
N/A
[optional] What gif best describes this PR or how it makes you feel?