Using Angle Brackets

46 views
Skip to first unread message

Josivan de Souza

unread,
Apr 23, 2020, 7:11:34 PM4/23/20
to yuml
I was using angle bracket is my diagram as a kind of placeholder. It does not work anymore.. How can I fix it?

My example

[Authorizer|-name:string;-config:FeatureAbbreviations]
[Client Configuration|-id:string;-secret:string;-featureAbbreviations:string]
[Feature Abbreviations|]
[User Info|-claims]
[Authorizer]-1>[Feature Abbreviations]
[Client Configuration]++-0..*>[Feature Abbreviations]
[User Info]-[note:Should have custom:feature_<abbreviation> as true{bg:yellow}]
[Feature Abbreviations]-[note:IAM WFS TMS OBJ{bg:yellow}]

<abbreviation> is the placeholder

Tobin Harris

unread,
Apr 23, 2020, 7:26:24 PM4/23/20
to yuml
Sorry about that. Interestingly it's parsing fine, but when the diagram gets "prettied up", that's where it's failing in the XML library.

I'll keep looking.

T

Tobin Harris

unread,
Apr 23, 2020, 7:33:17 PM4/23/20
to yuml
Hi, ok I found the issue.

Here's your diagram working.

Josivan de Souza

unread,
Apr 24, 2020, 4:36:11 AM4/24/20
to yuml
Hi. I had a problem with another one.

I had to change from:
// Entity Model IP-APP
[Assignment|id:INTEGER|professionalId:INTEGER;clientId:INTEGER;startDate:DATE;endDate:DATE;isInternal:BOOLEAN;moreInfo:STRING|createdAt:DATE;updatedAt:DATE]
[Client|id:INTEGER|name:STRING|createdAt:DATE;updatedAt:DATE]
[CommonRecord|id:INTEGER|description:STRING;parentId:INTEGER|createdAt:DATE;updatedAt:DATE]
[Consultant|id:INTEGER|email:STRING;name:STRING;phone:STRING|createdAt:DATE;updatedAt:DATE]
[Professional|id:INTEGER|name:STRING;dutchSpeaker:BOOLEAN;uniqueSellingPoint:STRING;pitch:TEXT;countryId:INTEGER|createdAt:DATE;updatedAt:DATE]
[ProfessionalDetail|id:INTEGER|professionalId:INTEGER|createdAt:DATE;updatedAt:DATE]
[User|id:INTEGER|email:STRING|createdAt:DATE;updatedAt:DATE]
[Permission|id:INTEGER|description:STRING;shortName:STRING|createdAt:DATE;updatedAt:DATE]
[UsersPermissions|userId:INTEGER;permissiondId:INTEGER|createdAt:DATE;updatedAt:DATE]
[CommonRecord]1-0..*(parentId)>[CommonRecord]
[User]1-0..*>[UsersPermissions]
[Permission]1-0..*>[UsersPermissions]
[Professional]<1 (countryId)-1[CommonRecord]
[Professional]<1 (livingPlaceId)-1[CommonRecord]
[Professional]1-0..*>(professionalId)[Assignment]
[Professional]1-0..*>(professionalId)[ProfessionalDetail]
[Client]1-0..*>(clientId)[Assignment]

to:
// Entity Model IP-APP
[Assignment|id:INTEGER|professionalId:INTEGER;clientId:INTEGER;startDate:DATE;endDate:DATE;isInternal:BOOLEAN;moreInfo:STRING|createdAt:DATE;updatedAt:DATE]
[Client|id:INTEGER|name:STRING|createdAt:DATE;updatedAt:DATE]
[CommonRecord|id:INTEGER|description:STRING;parentId:INTEGER|createdAt:DATE;updatedAt:DATE]
[Consultant|id:INTEGER|email:STRING;name:STRING;phone:STRING|createdAt:DATE;updatedAt:DATE]
[Professional|id:INTEGER|name:STRING;dutchSpeaker:BOOLEAN;uniqueSellingPoint:STRING;pitch:TEXT;countryId:INTEGER|createdAt:DATE;updatedAt:DATE]
[ProfessionalDetail|id:INTEGER|professionalId:INTEGER|createdAt:DATE;updatedAt:DATE]
[User|id:INTEGER|email:STRING|createdAt:DATE;updatedAt:DATE]
[Permission|id:INTEGER|description:STRING;shortName:STRING|createdAt:DATE;updatedAt:DATE]
[UsersPermissions|userId:INTEGER;permissiondId:INTEGER|createdAt:DATE;updatedAt:DATE]
[CommonRecord]1-0..*(parentId)>[CommonRecord]
[User]1-0..*>[UsersPermissions]
[Permission]1-0..*>[UsersPermissions]
[Professional]<1 (countryId)-1[CommonRecord]
[Professional]<1 (livingPlaceId)-1[CommonRecord]
[Professional]1-0..* (professionalId)>[Assignment]
[Professional]1-0..* (professionalId)>[ProfessionalDetail]
[Client]1-0..* (clientId)>[Assignment]

The difference is here:
[Professional]1-0..*>(professionalId)[Assignment]
should be
[Professional]1-0..* (professionalId)>[Assignment]

Thanks again

Tobin Harris

unread,
Apr 24, 2020, 8:20:45 AM4/24/20
to yuml
Thanks for reporting that. 

Yah, that's going to be a harder one to fix with the new parser :) I'll see what I can do. Did that syntax

You can put the > either side of the label, but the label can't be split around the >. I didn't realise this worked before, probably the very relaxed nature of RegEx for the I used to do!

T

[Professional]1->0..*(professionalId)[Assignment] 
[Professional]1-0..1 (professionalId)>[Assignment]

Chris Roberts

unread,
Oct 20, 2023, 9:10:56 AM10/20/23
to yuml
Try this:

[BashScript| args : List\<String\>]


-Chris
Reply all
Reply to author
Forward
0 new messages