Allow ignoring query parameters on list views

[tomaszn]

I'd like to parametrize views using links. Unfortunately list views use all query parameters to filter data, so context.list becomes empty. This change allows ignoring prefixed parameters, and the prefix is configurable.

[sheppard]

Thanks, this is useful though I have some thoughts about the API.

1. Could this be a list of keywords instead of a prefix? You could still use prefixed parameters as long as you list all of them in the configuration.
2. Could this be set at the wq/model.js configuration level rather than in wq/app.js? Different models might use different non-filtering keywords. (If you use the same keywords on all models you could just repeat the configuration for each model).

I ask this because I would like to synchronize this functionality with wq.db, specifically the (currently undocumented) attribute on views called ignore_kwargs (see filters.py). We would change that from a view attribute to a configuration option that would match whatever we do here.

[sheppard]

An alternative (or addition) to making this configurable might be to have wq/model.js read from the list of model fields and only filter on the ones that match. This is essentially what filters.py does here. One tricky part is that filters.py uses any and all Django Model fields, whereas wq/model.js would only have access to writable serializer fields (since that's what is used to generate the form configuration). I could see a case where you would want to compute and store a read-only field and have it available for filtering.

[tomaszn]

Thanks for your feedback! I think I would favour this automatic ignoring of filtering criteria, because it means editing one files less when introducing another parameter. It also means one configuration option less. (And if it is not implemented, we probably should display or log a warning.)
When filtering the parameters we need to remember also about the model.functions which are available for filtering the list.

[sheppard]

I implemented this to default to defined fields, but allow override via config.

• By default, only writeable fields (listed in form) and computed fields (in functions) will be used for filtering.
• Server-defined read-only fields can be added via the new filter_fields array.
• If a filter includes query parameters not defined in form, functions, or filter_fields, the parameters will be ignored. Since this may be unexpected behavior, a warning will be logged unless the fields are explicitly listed in the new filter_ignore option.
• If there are model fields that should always be ignored when filtering, they can be defined in filter_ignore.