When the query is present in the query parameter, and the page is refreshed:
Current Behavior: The query is applied but it shows filter type as SQL
Expected Behavior: The query should be applied with appropriate filter type view in the filter section.
When a filter is saved:
Current Behavior: filter_builder is being sent in the payload.
Expected Behavior: filter_builder will not be sent, instead filter_query will have the query.
When a filter is saved:
Current Behavior: filter_builder is being sent in the payload.
Expected Behavior: filter_builder will not be sent, instead filter_query will have the query.
When a saved filter is applied:
Current Behavior: The filter query is applied but it always shows the filter view as SQL mode.
Expected Behavior: The filter should be applied as per the filter type and the respective view should be showed in the filter bar.
Editing a saved filter:
Current Behavior: filter_builder field is sent as per the filter_type in the PUT call
Expected Behavior: filter_builder field will not be sent in the PUT call
New URL query parameter on filter application:
Expected Behavior: A new URL query parameter should be added to represent filter_type when a filter is applied, to track and maintain the filter type within the URL.
Added
filter_query
to all types of filters.Testing Scenarios:
filter_builder
will not be sent, insteadfilter_query
will have the query.filter_builder
is being sent in the payload. Expected Behavior:filter_builder
will not be sent, insteadfilter_query
will have the query.filter_builder
field is sent as per thefilter_type
in the PUT call Expected Behavior:filter_builder
field will not be sent in the PUT callfilter_type
when a filter is applied, to track and maintain the filter type within the URL.