[MGNLCTS-103] Exported translation file in Magnolia 6.1 is empty Created: 12/Apr/19  Updated: 29/Apr/19  Resolved: 23/Apr/19

Status: Closed
Project: Content Translation Support
Component/s: None
Affects Version/s: None
Fix Version/s: 2.4

Type: Bug Priority: Neutral
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: regression
Remaining Estimate: 0d
Time Spent: 3.85h
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-7431 Replace I18n Proxytoys instrumentatio... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Sprint: Foundation 8, Foundation 9
Story Points: 1

 Description   

Problem occurs at info.magnolia.translation.TranslationModule#supportsFieldDefinition:
all supported field definitions are skipped due to the fact that now a class name can contain a suffix starting with $ByteBuddy 

 


Generated at Mon Feb 12 00:33:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.