FEATURE: Retranslation - #95
Conversation
FEATURE: Inspector retranslation
…ration-handling Handle Node Operations in StaleTranslation Projection
Retranslator & Inspector UI
|
From what I could see when checking the core, the UI part does not pass a I could not test or try to fix the issue locally yet, as the |
Retranslation neos9
I made the parameter required in the endpoints, the UI part still needs to be adjusted |
add contentrepositoryid to both endpoints
Resolves conflicts after the branch's base (retranslationUpmerge, PR sitegeist#95) was merged into 3.x and released as v3.3, and 3.3 then gained independent retranslation work (notably whole-workspace retranslation). Key resolutions: - Retranslator: keep this branch's cross-workspace per-node engine, renamed retranslateNode -> retranslateSubtree to match released v3.3; keep 3.3's retranslateWorkspace() + helpers (both whole-workspace paths kept, alongside FullWorkspaceSynchronizer). Callers renamed accordingly. - ReferenceDimensionSpacePointResolver: adopt 3.3's options.referenceLanguage config key; keep this branch's findAllTargetDimensionSpacePoints() API. All dimension-config fixtures/settings updated to options.referenceLanguage. - StaleTranslationProjection: keep this branch's handlers (empty structural rows retained); keep 3.3's automaticTranslation guard where auto-merged. - Neos.Ui: take 3.3's contentRepositoryId + isPending; Plugin.js rebuilt. - CI/tooling: take 3.3's phpcs.xml.dist + phpstan scanDirectories; keep this branch's Behat job. - Behat: keep this branch's suites; 3.3's workspace-retranslation scenario preserved in a new standalone WorkspaceRetranslation.feature.
6 participants
This adds the 2.x / Neos 8 retranslation feature to 3.x / Neos 9.
uses a custom projection to track stale translations on property level to avoid unnecessary retranslations.