[ad-hoc filters] Remove legacy split in /explore #5533
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes the unnecessary step of splitting ad-hoc filters into legacy filters for the
/explore
endpoint. This merely unnecessarily pollutes (in a non-harmful way) the form-data (including that in the URL) with legacy constructs. These clauses are ignored given that theadhoc_filters
field is guaranteed to exist (by construction).Note the only place we currently need to split ad-hoc filters to legacy (base) filters in the
BaseViz.query_obj(...)
as the query logic still uses the legacy constructs. Note a migration is not needed here given the code correctly converts and then removes the legacy constructs, but could be merited for cleaning up erroneous fields in the form-data.to: @GabeLoins @graceguo-supercat @michellethomas @mistercrunch @timifasubaa