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

Translation history modal to show leveraging and integrity check messages #960

Merged
merged 7 commits into from
Jul 14, 2023

Conversation

aurambaj
Copy link
Collaborator

No description provided.

@aurambaj aurambaj changed the title Ja/import target comment Translation history modal to show leveraging and integrity check messages Jul 13, 2023
@aurambaj
Copy link
Collaborator Author

new modal:

Screenshot 2023-07-13 at 1 14 21 AM Screenshot 2023-07-13 at 1 13 00 AM

old modal: Screenshot 2023-07-13 at 1 11 18 AM

…atch import

we're currently not saving the error for that import implementation while we do it in other imports, see AbstractImportTranslationsStep/ImportExportedXliffStep
@aurambaj aurambaj marked this pull request as ready for review July 13, 2023 20:16
Copy link
Contributor

@hylstonnb hylstonnb left a comment

Choose a reason for hiding this comment

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

Thank you for these chances. Adding a few comments

webapp/package-lock.json Show resolved Hide resolved
@ResponseStatus(HttpStatus.OK)
@JsonView(View.TranslationHistorySummary.class)
public List<TMTextUnitVariant> getTextUnitHistory(
@PathVariable Long textUnitId,
@PathVariable Long tmTextUnitId,
Copy link
Contributor

Choose a reason for hiding this comment

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

as you are just changing a path variable name, I don't think there is anything relying on that name, right?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

exact, no other change beside making the code more readable. With the previous name it was not clear at first sight which id exactly it was.

Add TMTextUnitVariantComment to the TranslationHistorySummary JSON view. This API will now include the variant comments in the payload.

This will be used by in the frontend to surface more information related to leveraging, and integrity checker failures.
so that next commit just show relevant change
this relates to running integrity checker during import localized asset but not pursuing the other update at the moment
…ages

This helps to bring visibility to the translation status by showing the root cause of a "rejected" string or a "need translation" string due to leveraging or integrity checks.

If there are "comments" on a text unit variant then an accordion will be display. Expanding the accordion will show log style information, typically leveraging and integrity checks messages
@aurambaj aurambaj merged commit f0a8ef7 into master Jul 14, 2023
2 checks passed
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.

2 participants