@shellscape Hey @shellscape not strictly opposed to it, but would probably prefer retaining it as I still use it on a couple legacy apps, and had intention of revamping at some point. Would be happy to add you as maintainer if that suits your needs?
@calebwright careful not to take on more than your team can maintain long term. What starts out as a simple replacement for a few tabs has a tendency to quickly grow into a large reporting app lol
@calebwright Great article Caleb! I particularly liked the do’s/dont’s section, it’s very easy to fall into some of those traps, even when you know better. While I generally agree with the idea of replacing spreadsheets with apps, I do think one also has to be (cont)
@ScriptedAlchemy@PierB Is most of the data from API requests? I’m not sure whether other API abstraction libs support this currently, but I’m about to publish an update to jsonapi-react that allows you to flag non-hydrated queries
@ScriptedAlchemy 2) The component that fetches/renders the links has no state transitions (at least that required react), so we skip hydrating it completely!
@ScriptedAlchemy 1) We’ve been able to skip hydration altogether surprisingly often. E.g. we have a page that renders a dynamic list of almost 2000 urls, that had a huge API payload (https://t.co/am1HlNqlv9).