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

Update to CMCC 2406.1.0 #73

Merged
merged 134 commits into from
Jan 28, 2025
Merged

Update to CMCC 2406.1.0 #73

merged 134 commits into from
Jan 28, 2025

Conversation

mmichaelis
Copy link
Member

@mmichaelis mmichaelis commented Jan 6, 2025

To-Dos

Development

  • Remove GitHub Action (using a new approach, updating ci/develop is no longer required)
  • Update Workflow State Overview for new state "Redelivered".
  • Check for required documentation updates for the new "Redelivered" state.
  • Update CHANGELOG.md
  • Update CHANGELOG.md with recent changes (submission not found, invalid connector key)
  • Manual tests: Add scenario for "submission not found" (switch to second connector key)
  • Manual tests: Add scenario for invalid connector key.
  • Manual tests: Test with "Submission Error" (instruction mode: html)
  • Release Note about (minor) breaking change regarding instructions.
  • Contract Test: Prefix all submission names with an easy to identify name.
  • Contract Test: Use results from Contract Test for validation, for example, of the instruction text and/or submitter.
  • Contract Test: Add test for "no submission" by switching connector keys (and skip tests, if there are not multiple connector keys available)
  • Continue Unicode Instructions. As it seems, Plane 1 and above characters are always unsupported.... what to do now?
  • Now that we have found a solution for submission instructions, it is the same with submission names that must only contain BMP characters. We may need to partially reinvent the wheel...

Review

  • Validate labels for "Redelivered" state.

After Release

  • Update Release Notes (Draft below)
  • Delete branch ci/develop (we do not need that anymore)

The following is the proposed release note, once merged to main.


GlobalLink Connect Cloud for CoreMedia Content Cloud v12.2406.1.0

Despite adapting the connector to CoreMedia Content Cloud v12.2406.1.0, we hardened the connector in these aspects:

  • Introduced a defined behavior for the undocumented submission status REDELIVERED.
  • Fixed submission instruction handling to deal with its features (HTML content) and limitations (character types).
  • Fixed submission name handling to deal with its limitations (character types).
  • Hardened the connector in case of submission errors (an extra state reachable in the GCC backend).
  • Hardened the connector for "submission not found" scenarios that may occur due to wrong or connector key settings.

More detailed information and upgrade notes are available within the Changelog hosted on GitHub Pages.

Change referenced versions to 2406.1.
Now using up-to-date version 2.5.0.
* Use version 2406.1.0
* Align Jangaroo dependencies with 2406.1.0 release.
Change referenced versions to 2406.1.
Update to version 2406.1.0.
This commit should be dropped prior to merge.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
Applying static code analysis fixes.
@mmichaelis mmichaelis changed the base branch from main to develop January 23, 2025 08:03
For consistency, a replacement strategy `none` seems to make sense.
While the same could be achieved setting `characterType` to
`unicode` (as this just ignores replacement strategies), looking
at both enums from an independent perspective, the "none" replacement
type is missing.
At least when using this adapter also for other translation agencies
or as soon as GlobalLink supports Unicode, a hint should exist, how
to configure the adapter. Added an upgrade note for that.
While artificial if used "as intended", the replacement strategy should
be able not to provide unexpected results for unexpected successful
empty matches, like for `.*`.
As the HTML instructions would just ignore leading spaces, we make them
non-breaking-spaces instead, now.
`textTransform` is easier to read and understand (especially, if you
need to adjust it), compared to the previous `textType`.
Replacement operations moved to other classes now.
Before, all leading spaces got transformed to one ` `. Instead,
we should keep the same number of characters.
Just moving connector key validation.
@mmichaelis mmichaelis marked this pull request as ready for review January 27, 2025 08:41
The GCC logging is much too verbose to include it into our stdout.
Just logging it to file now.
The only relevant authorization item that should not appear is the
API-Key. A connector key is no real secret. Also, it should be the
task of the `GCFacade` to hide secrets, if any, not ours.

Removing this extra effort.
The GCC API is very verbose on INFO level. Decided to reduce the
verbosity on delegation to `debug`.

Also, added the original log-level for information purpose.
Aligning with other configuration tests.
@mmichaelis mmichaelis merged commit 0da43cb into develop Jan 28, 2025
3 checks passed
@mmichaelis mmichaelis deleted the gcc-cmcc-12-2406.1.0 branch January 28, 2025 11:22
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.

1 participant