userInfo = {
"_EntityModeler" = {
documentation = "doc for EMRTreatmentStep\n<ul>\n\t<li>a list entry</li>\n</ul>";
};
};
Tried different KV-paths in the template file but failed whenever I explicitly used the key “_EntityModeler” with/out “_”, with/out capital “E”. Using “_” results in a syntax error during generation.
Accessing the user info dict itself works
Using
${entity.userInfo}
results in
{_EntityModeler={documentation=doc for EMRTreatmentStep
<ul>
<li>a list entry</li>
</ul>}}
Which is great so far but two key too high in the key path.
However going deeper only dumps the given path itself into the result
${entity.userInfo.entityModeler}
results in
${entity.userInfo.entityModeler}
I expect this to result in something like
{documentation=doc for EMRTreatmentStep
<ul>
<li>a list entry</li>
</ul>}
Seems like EOGenerator explicitly ignores the key “_EntityModeler”
I can put my own javaDoc key into the user info dict, this works, but the text input field in WOLips EntityModeler is way too small in the userInfo editor.
What is the documentation good for if I cannot access it?
Any ideas?