When I first wrote the Query Language used in the ResourceFilter I based it off 
of a "Resource Query Language" combined with a more familiar JCRSQL2 syntax.  
Effectively it's a 'key' = 'value' filter  combined with basic logic and 
grouping.
I looked at the SlingQuery implementation which is based off of JQuery, it has 
a cleaner syntax in a lot of cases but doesn't do some of the things I 
personally need like the ability to compare two properties. I'm working on 
getting ResourceFilter release ready and now is the time to make any changes to 
the language. Either additions, modifications, or adopting a new paradigm like 
an implementation  of GraphQL, because it's the new hotness. I was wondering if 
any of you had thoughts on the subject, strong opinions, or a wish list. 

TIA.

- Jason

Reply via email to