Allow REGEX filtering to support AND/OR operations about symphonycms

[designermonkey]

After reading your answer, and thinking, the question arises that if we were to do this, how would we advise to terminate the regex statement?

Because normal characters can be used, a user would possibly expect to use , or + in their statement too. How do users get to use these characters normally? Are they escaped somehow??

[brendo]

You can urlencode them and they'll work. I've had to do it before with date filtering, aka. later than today + 1 week

It's an interesting point, I suppose at the moment if you use a , or + in a regexp it will probably break the filtering.

[designermonkey]

Yeah. The way regex was meant to work originally was to take the entire string after the regexp: string and check for that, but like you say, I'm not sure what would happen using + or, at present.

I asked the question merely to prompt debate on it, but it is very advanced filtering, which may just bring more confusion to the table, which we obviously want to avoid.

I have got around my issue by customising the DS slightly to check for the existence of the params and alter the filter based on that.

[brendo]

Going to close this, regexp: is a bit of an oddity and I agree with you, it's pretty advanced filtering :)

Perhaps this style of filtering can be revisited after potential datasource changes with #699