Open mseaton opened 11 months ago
If that's right then this really a metadata regionalization/localization feature so that the database looks "local" to consumers in country. Then maybe, rather than the
_translate_
directive, we could use_localize_
(or_L10n_
)?
Sure, we can have this named whatever we want. I'll take direction from you on this, and make it so.
Note, if this approach is approved, then there are likely additional changes to expand this beyond the encounter type domain, by changing other metadata loaders to extend the
BaseMetadataLineProcessor
rather than theBaseLineProcessor
and then update the way the set the name and description properties.For now, this works and is tested against the
EncounterType
domain.We'll also need to update the README and Release Notes. I can add that in if this is agreed on as a general approach. I expect there may be alternative ideas for what the constant is named (currently "
_translate_
", but I assume others may have better ideas here).