Hi @wbinnssmith! This library looks really promising and I have a few questions about it to see if it will work for me.
I have a setup with deeply nested entities and am currently using normalizr out of the box. So I am wondering how using just plain normalizr compares to using this middleware? Is it more of an architecturally cleaner choice on where should normalization happen or are there other advantages that I might be missing?
Any future plans to support non FSA actions? Thats probably the biggest thing which is stopping me from jumping on it right away.
This is just meant to apply a convention around the data and its schema to avoid the repetition of continually normalizing data in your action creators. Whether or not that is cleaner is a subjective thing for sure, but I've appreciated the declarativeness in my own apps.
Going with the above, a lot of the benefit of this is driven by convention and I'd rather not expand the api too much. That said, with earlier versions of this module I experimented with customizing where to find the payload and schema inside the action.
If this is something folks would find useful I'd be happy to continue exploring that and of course PRs are always welcome.
Hi @wbinnssmith! This library looks really promising and I have a few questions about it to see if it will work for me.
normalizr
out of the box. So I am wondering how using just plainnormalizr
compares to using this middleware? Is it more of an architecturally cleaner choice on where should normalization happen or are there other advantages that I might be missing?Thanks again, and happy new year!