Problem: This is a follow-up ticket to #950, which is known to produce odd results in some cases. We tested multiple versions of that implementation and concluded the ideal solution is to not inject anything in the generated query for ignored search terms --we elected not to try to pull this off before launch. For launch, we allowed #950 to inject cts.trueQuery or cts.falseQuery.
Here's the point in a long Teams conversation identifying another issue with #950 and when we concluded to roll with it and open this ticket: nail in coffin.
Problem: This is a follow-up ticket to #950, which is known to produce odd results in some cases. We tested multiple versions of that implementation and concluded the ideal solution is to not inject anything in the generated query for ignored search terms --we elected not to try to pull this off before launch. For launch, we allowed #950 to inject
cts.trueQueryorcts.falseQuery.Here's the point in a long Teams conversation identifying another issue with #950 and when we concluded to roll with it and open this ticket: nail in coffin.
Expected solution: TBD
Needed: