Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    This seems like the most 'correct' answer and storing literal functions in state was a quick fix that will be change to a more traditional method before release. Commented Jun 23, 2016 at 17:07
  • 1
    Sure. One related approach you may look at is storing some kind of filter name or identifier in your state, and then using that as a key to look up the actual filter function in a component or a selector, similar to the approach suggested for managing dialog components at stackoverflow.com/questions/35623656/… . Commented Jun 23, 2016 at 17:43
  • 1
    Examples would be nice Commented Nov 8, 2016 at 22:15
  • All links are broken. Commented Mar 3, 2018 at 23:31
  • We did recently update the docs build tool, which changed URLs. It's supposed to redirect the old URLs, but that seems to not be working right. I'll update the links. Commented Mar 3, 2018 at 23:54