Mario, Thanks for the bracket fix! (I should have caught that, but was getting bleary-eyed.)
When you say, "you mainly test with tiddler titles, and not fields. Even if you have strange field names...," I'm not sure what you mean. I have focused mostly on having strange field names that correspond to strange tiddler titles, partly because I anticipate that the newly open field-name space will get half its value from letting field names correspond to tiddler titles. And because of the centrality of Shiraz to my own workflow, I have been testing how Shiraz (especially dynamic tables) behaves with the new field name possibilities. My other anticipated use for strange field names is to serve as compact headings in dynamic tables, where the difference between "tennis" and 🎾 or "recyclable" and ♻︎ (in a field with √ or X values) is conservation of horizontal table space. So: What other kinds of tests do you (and others) see as important? Though my coding skills are minimal, the challenge to test the limits of a new feature is one area where I enjoy chipping in as best I can. -Springer On Friday, July 23, 2021 at 8:37:23 AM UTC-4 PMario wrote: > Hi, > Nice tests, but you mainly test with tiddler titles, and not fields. Even > if you have strange field names in your tiddlers. > > > https://springerspandrel.github.io/tw/new-json-tw-experiment.html#Show%20related%20field-table%20(ViewTemplate) > > .. The filter is probably broken, because the number of opne/close braces > are wrong. The last closing brace is missing ...first[]] > > BUT I didn't test the code. > > -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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0ae2a84a-d7a8-426e-8aeb-0e629cfa2b92n%40googlegroups.com.
