railsant/somatics_filter

Rewrite of redmine_filter

somatics_filter's Issues

Custom Name on Filter

Filter accepts custom name. Can be done by accepting options[:name] by has_filter

Caching of Last Query

Save the last query in the session so as to persist the query on the next request until the user presses the clear request.

Store Custom Filter

• Name
• Applied Filters
• Applied Fields

Add Save as default

We can have the save as default to have the default column view and filter view when accessing the model.

Handling for Invalid Filter Type

Currently the error dump is
You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.first

Should be "Somatics::Filter::UnknownFilterType 'filter_type'

Association Filtering

Allow to set filter on association information, e.g. Post has many comments and post should accepts filter comments_count.

Saved Query should belongs to an admin

There is a field called whodunnit but is not yet used now.

Preserve the Filter in Session

As in previous version, the filter query shall persist across the session so that when page refresh, the query will still persist.

Change include SomaticsFilter::ActionController::CoreExt to class method persist_last_query

Merge Into Somatics

Allow Multiple Select in List View

As in previous version, there exist a multiple select for a list view.

Cache Last Query will cache the save/delete params

Editing of Saved Query

Refer to Redmine

Bug: The List Filter may cause problem on loading environment

When the Filter contains some code likes "Comment.all" and the table "comments" does not exist, there will be a bug that the migration cannot be executed.

Improve the documentation on the usage

There are use cases not documented (e.g. type of filter, available options). There are constraints not documented (e.g. div should have id content due to the use of Ajax).

Reduce Length of Query Params

Replace the following params name

• somatics_filter_query => f
• is_set => s
• operator => o
• value, value1, value2 => v, v1, v2

Multiple Select on Value for List Filter

Add multiple select for list filter. Try to use :field_in => [v1, v2].

Ordering of Filters

The Filter form rendered has no order on the available filters. The order should be the same as that of has_filter calls or accepts options[:order].