On Monday, May 3, 2021 at 3:37:34 PM UTC+2 PMario wrote: > 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. >
We may have to have a look at the spec: https://tools.ietf.org/html/rfc3986 ... Just to be sure, that we don't violate best practices too much ;) -m -- 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/31c6cf90-8f97-44b1-8858-35fc57bcd696n%40googlegroups.com.
