#setFilter is a terrible API. Change it. about filtered-collection HOT 3 OPEN

I have been considering the usage of this library, and I believe the ideal solution would be to limit the API to the constructor only.

#reFilter will be used to re-execute a filter.
new ...(null, {collection: {}, filter: function() {}}) will be the way to set a collection and a filter, changing filters will be disabled as it would make much more sense to create another filtered collection along with it's appropriate filter and sub-collection

from filtered-collection.

I notice there are quite a few people using this tool. Is there any objections to this? This would be quite the API-breaker.

from filtered-collection.

So far I only used it to set the filter once and this would benefit from being able to add the filter function as a parameter in the constructor.

But just now I wanted to look up an API to add more filters to an already filtered collection. So something like addFilter() would be handy.

The API could be extended both ways without breaking changes i guess.

from filtered-collection.