X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.25a (ClamAV 0.103.11/27272) X-Junk-Score: 0 [] X-KAS-Score: 0 [] Return-Path: Received: from mail01.rucotec.ch ([65.21.159.64] verified) by post.selbstdenker.com (CommuniGate Pro SMTP 6.3.18) with ESMTPS id 32486680 for webobjects-dev@wocommunity.org; Sat, 11 May 2024 14:55:18 +0200 Received-SPF: pass receiver=post.selbstdenker.com; client-ip=65.21.159.64; envelope-from=markus.ruggiero@rucotec.ch Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id DD0415E039 for ; Sat, 11 May 2024 14:55:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rucotec.ch; s=dkim; t=1715432107; h=from:subject:date:message-id:to:mime-version:content-type; bh=EgOYQwhWE3F/VfKOXRYxQRRfX+1stdR8Ka/eOTjjYwM=; b=RHEkpa3P5QK23D3XMYh2F4iU7dAJ9yQXLxZK2pY/XZ7TOeW32PnZyVxCvhY3h6qn9xWZGz WvKzbHUydJ+TA9XnhxwvzNSngKKJV5UdgE8yHQwAp9HkKwGJB9wTkyCqaDaIIUPR1LPd/Q AL/jnYanu6sAlhRWJmcGT6+6g02eW2ffe+Y7tCB/xbIpDN5p8bzLqwWIedt4hnTXbrdsul J8bal9ITK0Ie6xVCo91xwfctAd1/s3p5tUCjULerzaJK6kuvDHl3MP9Aju7FpQZNxCDE+B WPC4sB7qgEnjksLOyoAxZ+T2RWHGCY78vQp38V9ArP8uw38hLvwQbwsFEhfoWQ== From: "Markus Ruggiero (rucotec)" Content-Type: multipart/alternative; boundary="Apple-Mail=_B29DB474-12A2-4919-B38F-26BB4484D804" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\)) Subject: How can I access EOEntity userInfo documentation with EOGenerator? Message-Id: Date: Sat, 11 May 2024 14:54:52 +0200 To: WebObjects & WOnder Development X-Mailer: Apple Mail (2.3774.500.171.1.1) X-Last-TLS-Session-Version: TLSv1.2 --Apple-Mail=_B29DB474-12A2-4919-B38F-26BB4484D804 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 When creating documentation for an entity in the Documentation tab in = EntityModeler the resulting doc is put into the userInfo dictionary. How = can I access this with EOGenerator? userInfo =3D { "_EntityModeler" =3D { documentation =3D "doc for EMRTreatmentStep\n
    \n\t
  • a = list entry
    • \n
";=20 };=20 };=20 Tried different KV-paths in the template file but failed whenever I = explicitly used the key =E2=80=9C_EntityModeler=E2=80=9D with/out = =E2=80=9C_=E2=80=9D, with/out capital =E2=80=9CE=E2=80=9D. Using =E2=80=9C= _=E2=80=9D results in a syntax error during generation. Accessing the user info dict itself works Using ${entity.userInfo} results in {_EntityModeler=3D{documentation=3Ddoc for EMRTreatmentStep
  • a list entry
}} 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=20 ${entity.userInfo.entityModeler} I expect this to result in something like {documentation=3Ddoc for EMRTreatmentStep
  • a list entry
} Seems like EOGenerator explicitly ignores the key =E2=80=9C_EntityModeler=E2= =80=9D 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.=20 What is the documentation good for if I cannot access it? Any ideas? --Apple-Mail=_B29DB474-12A2-4919-B38F-26BB4484D804 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 When creating = documentation for an entity in the Documentation tab in EntityModeler = the resulting doc is put into the userInfo dictionary. How can I access = this with EOGenerator?

    userInfo =3D {
        "_EntityModeler" =3D = {
      =       documentation =3D "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 = =E2=80=9C_EntityModeler=E2=80=9D with/out =E2=80=9C_=E2=80=9D, with/out = capital =E2=80=9CE=E2=80=9D. Using =E2=80=9C_=E2=80=9D results in a = syntax error during generation.

Accessing the = user info dict itself = works

Using
    = ${entity.userInfo}

results = in
    =  {_EntityModeler=3D{documentation=3Ddoc 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=3Ddoc = for EMRTreatmentStep
    <ul>
<li>a list = entry</li>
    </ul>}

Seems like = EOGenerator explicitly ignores the key = =E2=80=9C_EntityModeler=E2=80=9D


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?





= --Apple-Mail=_B29DB474-12A2-4919-B38F-26BB4484D804--