Saq Imtiaz

Quick update: the `module-exports[]` operator turns out to not be coherent since not all module types have named exports, and some exports (for example some filters) are not available until...

@linonetwo a `widgets[]` operator would be more consistent, we already have a `deserializers[]` operator, see https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/filters/deserializers.js However, to avoid ending up with a multitude of operators that query the presence...

@Jermolene that is a good example indeed. Here is a very quick attempt at doing something similar with a filter: 

@Jermolene that is terrific, thank you. As you say we can do much more with the presentation too, making it interactive, tying in documentation etc. In an ideal world we...

Executing in a browser console for a TiddlyWiki tab: `JSON.stringify($tw.wiki.parseFilter("[tag{$:/MySpecialTag}hasget[text]!is[blank]]"),undefined,4);` We get: ``` [ { "prefix": "", "operators": [ { "operator": "tag", "indirect": true, "operand": "$:/MySpecialTag" }, { "operator": "has",...

Just occurred to me that the filter parse tree looks a bit different in 5.1.23 pre-release with the support for multiple operands: ``` [ { "prefix": "", "operators": [ {...

I worked on this a bit late last year and one of the things that would make this easier in terms of mapping the output of the parser back to...

Posting some details of my work on this so far so as to keep the ball rolling when I have the time to get back to it. The image below...

@Jermolene I'll try to find time to pick back up on this in a week or so. I need to update the code to handle multiple filter operands and filter...

Interleaving the explanatory text with the syntax breakdown: