(I posted this on the discourse channel as well - apologies for cross-posting)
I’ve been using java-libs to flatten a template, i.e., apply all of its constraints and print the resulting archetype. This is working wonderfully - but the end result is missing terminology and language bindings - this makes it rather unusable when generating a UI, for instance.
Updating the Flattener code to keep these bindings is an option, but seems complex: internal node-ids would have to be updated (these are typically re-used in archetypes, e.g., at0004) to have unique terminology bindings across the archetypes.
(I posted this on the discourse channel as well - apologies for cross-posting)
I’ve been using java-libs to flatten a template, i.e., apply all of its constraints and print the resulting archetype. This is working wonderfully - but the end result is missing terminology and language bindings - this makes it rather unusable when generating a UI, for instance.
Updating the Flattener code to keep these bindings is an option, but seems complex: internal node-ids would have to be updated (these are typically re-used in archetypes, e.g., at0004) to have unique terminology bindings across the archetypes.
Thoughts?
Thanks, William