if we [want to fix callback caching], we should determine if we need a different caching solution. That solution may require coordination with the ops team for something like a Redis-based cache. We probably also want to consider changing the default to not memoize since many of the callbacks are not IO or CPU intensive and may not be worth the memory overhead.
[ ] This is something we can copy over from streamlit (screenshots if applicable)
Description:
As discussed in https://github.com/CodeForPhilly/chime/pull/481, our current implementation of callback caching isn't working as expected. Quoted from that discussion:
[ ] This is something we can copy over from streamlit (screenshots if applicable)