gistfile1.txt

your commit: http://github.com/anb/ruote-kit/commit/c5f95b0f025b48ffa560b00d1aa1e9a15f394169
you're doing an 'or' between the query strings there. i'm unsure if it shouldn't be an 'and'
especially when combining participant and fields query




I think you're right
"and" makes more sense
I will actually need it later




yeah, but not necessarily for the participant query. 'or' is equally important there, i suppose
(and implemented in rk at the moment)
 - kennethkalmer hat sich abgemeldet (Remote host closed the connection)




"or" the participants, "and" for the fields
and "and" the total ?




sounds reasonable




it's a bit confusing the "or" for the participants, no ?




yes, it's counter-intuitive.




I think "or" you can always run the query multiple times on client side, and "and" is more useful




but anding without having the possibility to or seems to be a no-go to me, too.
but each query means overhead.




true
another params to config behaviour ?




thinking about something like participant=foo|moo|mee&baz
but that's a complicated hell to parse, i suppose




could be




maybe participant=foo,moo,mee,+baz?
like search engine queries in ancient times#
participants marked with + are required (and therefore anded), others are combined by or




why not
so defaults to "or" and prefix + means "and"
but it's not trivial
argh '+' doesn't play well in the URL
 - kennethkalmer hat den Raum betreten




the same goes for &, so escaping ftw