Generate the "right" FilterKey instance even on parameterized filters

Description

Rules around object equality are the most tricky. Not sure we can do a good job at it.

Activity

Sanne GrinoveroJanuary 28, 2015 at 11:13 PM

Assigining to yu after book remark. but it has a low priority

7 years! good enough for "low priority" ?

Gunnar MorlingJanuary 27, 2015 at 5:52 PM

Sanne GrinoveroMarch 17, 2014 at 3:16 PM

would be about time to fix it then

To cache filters we now demand the user to provide a filter key to represent the (set of) parameters being used on a filter. This is easy to automate in a general purpose way, if you assume each named parameter is an Object (no primitives) and respects the equals contract.

Emmanuel BernardMarch 17, 2014 at 3:09 PM

Damn , I have no idea what this one is about, I would need 30 mins just to dig that up

Emmanuel BernardNovember 9, 2008 at 1:06 AM

Assigining to yu after book remark. but it has a low priority. As I said, I am not convinced we can do a good job and have safe rules to raise an exception when "we don't know how to do it".

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created November 9, 2008 at 1:04 AM
Updated October 31, 2017 at 12:33 PM
Resolved January 28, 2015 at 11:11 PM