Timeline for Custom Filters release announcement
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2019 at 11:23 | comment | added | Arulkumar | @BrianNickel Thanks for the fix. | |
| Aug 8, 2019 at 20:25 | comment | added | Brian Nickel StaffMod | The spacing will be fixed in the next build. | |
| Jul 3, 2019 at 17:06 | comment | added | TylerH |
@BrianNickel That's not how I recall it working in its first iteration (when SO added custom filters and then... took them away), but the problem is it's not reliably "what it says on the tin", because what it says on the tin is ambiguous. For me, it reads the way I interpreted it (and the nbsps reinforce that logic), not the way you interpreted (and apparently implemented) it. In light of this, I strongly encourage parentheses be injected for clarity.
|
|
| Jul 3, 2019 at 16:39 | comment | added | Brian Nickel StaffMod |
@TylerH This doesn't appear to be correct for question lists (maybe for question search, but that's a different beast and I have no clue how it parses things). If I do a and not b or b and not a, your logic would reduce to a and not a (aka nothing), but jquery and not javascript or javascript and not jquery does what it says on the tin.
|
|
| Jul 3, 2019 at 14:18 | comment | added | TylerH |
This is intended behavior because the space is really a substitute for parentheses; the not tags are grouped. In your example, this will return: questions (tagged with [tag:indiana-jones] (that are not also tagged w/ [tag:the-kingdom-of-the-crystal-skull] or [tag:star-wars])) and (not tagged with [tag:the-phantom-menace]) which is... probably not what you meant to do with that filter. cc @BrianNickel that could probably be made more clear. OP probably expects the or here to be splitting the filter into two distinct statements.
|
|
| Jul 1, 2019 at 23:16 | comment | added | Brian Nickel StaffMod |
This is a existing behavior that has probably been lingering for years. Whenever we encounter "and|or|-" in a query, we inject an after it. But we also inject a space between the "and" and "not", giving it two spaces that won't collapse together. This is old reusable code, so it'll take some digging to figure out if that's still needed or where else it might be used.
|
|
| Jul 1, 2019 at 18:12 | history | answered | Arulkumar | CC BY-SA 4.0 |