On Monday, May 3, 2021 at 8:35:10 AM UTC+2 TW Tones wrote: *Possible approach* > We could use the "_" underscore to delimit such "subFields" and create > additional fieldnames such as url_name and url_target. Then when I have > code dealing with "url" it can look for fields beginning url_ to find its > "subfields". I wonder if this compromises the available fieldnames or > others plugins and solutions that make use of the "_" underscore more often > than I do? > > Perhaps such fields that may have subfields could end with "_" eg; "url_" > meaning subfields exist for this fieldname. >
TW uses _canonical_uri for some "special handling already". So from my point of view it could use _uri SEE "i" not "l" for something special that expects additional info that can be used to define a proper html A tag. IMO most users will use url for their field names. just my thoughts. -mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a9dede26-f3bf-4b1a-997b-7f8d8e1eb0e3n%40googlegroups.com.
