Skip to content

EXPERIMENTAL: Add support for mireo repeatable fields #82

Draft
gradinarufelix wants to merge 3 commits into2.0from
feature-repeatable-fields-translation
Draft

EXPERIMENTAL: Add support for mireo repeatable fields #82
gradinarufelix wants to merge 3 commits into2.0from
feature-repeatable-fields-translation

Conversation

@gradinarufelix
Copy link
Collaborator

Introduces translation support for repeatable properties (e.g. JSON arrays) that contain translatable sub-properties.

Changes:

  • Add TranslatableRepeatablePropertyName class for handling repeatable fields
  • Extend TranslatablePropertyName with isRepeatable() method
  • Update TranslatablePropertyNames to support repeatable properties
  • Enhance TranslatablePropertyNamesFactory to detect repeatable fields
  • Extend NodeTranslationService to process repeatable field translations
  • Add configuration options for repeatable fields in Settings.yaml

@gradinarufelix gradinarufelix force-pushed the feature-repeatable-fields-translation branch from 956ad37 to df0ee04 Compare January 14, 2026 22:31
Introduces translation support for repeatable properties (e.g. JSON arrays)
that contain translatable sub-properties.

Changes:
- Add TranslatableRepeatablePropertyName class for handling repeatable fields
- Extend TranslatablePropertyName with isRepeatable() method
- Update TranslatablePropertyNames to support repeatable properties
- Enhance TranslatablePropertyNamesFactory to detect repeatable fields
- Extend NodeTranslationService to process repeatable field translations
- Add configuration options for repeatable fields in Settings.yaml
- Add @param PHPDoc for TranslatableRepeatablePropertyName constructor
- Add type assertion in getRepeatableProperties() return
- Fix array type annotations in normalizeRepeatableValue()
- Fix PHPDoc types in translateRepeatableProperty() to match native types
When repeatable properties are translated, they produce an array value.
The code was checking for a translation connector for array properties,
but if none was found (as is the case for repeatable fields), it would
keep the OLD target node value instead of applying the translated array.

This fix adds an else clause to use the translated array value directly
when no translation connector is configured for the property.
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