There should be an official example that covers:
* creating/updating entities with a remote backend;
* optimistic mutations.
Yes! :) I'd prefer this example to be without pagination, that is unless it's easily factored out by a new user.
@Barry Staes We can have one endpoint with pagination and another one without :)
Any example apps in mind that could cover all this?
It would also be great to include unit and integration testing!
I've made a start with one, it's got authentication, unit tests and uses reduxforms it's currently being used on a large crud app atm. It's a starting point
I've got something which might help started here: https://github.com/hedleysmith/redux-crud-example it uses Docker to build a simple backend API as well as the frontend app which I've found useful. Needs a fair bit of work still! Auth could be tricky to demonstrate without getting complex, focusing on CRUD might make things clearer?
I started working on this - but it's my experimental playground so I haven't shared before:
The stack I'm using:
- Karma (for testing)
- Enzyme for React specific testing
- CSS Modules
It's highly opinionated in a few places:
- e.g. Webpack uses a root resolver since I like to import from "containers/mycomponent"
- also Webpack is able to resolve directories if they have a JS file in them with the same name. This is due to create compact and shareable components (js/css/tests all in one place)
- StoreLoaders for data fetching
I'm working on https://github.com/vkbansal/andromeda, a small app for managing github stars.
My friend Matt has created something that you might find interesting, it's called meatier https://github.com/mattkrick/meatier
It's a meteor-like full stack application and it pretty much solves a lot of the higher mentioned requirements, running version is accessible at meatier.io
On top of that you should also check his newest creation, redux-operations https://github.com/mattkrick/redux-operations
the example is here: https://github.com/mattkrick/redux-operations-counter-example as it solves few unique problems as well! As always, your input and critique would be very appreciate.
I think the app needs to be more than just a boilerplate. The user should be able to download the code and get started pretty easily without doing too much. I'd like to work on this with everyone and see how this compares to my own solution I'm using in my app right now.
Also to help understand the codebase we should be clear about what the application is doing right upfront. Does anyone have a specific starting spot they like more or less? Eager to get started on this. :D
Redux is an entire ecosystem. I'd love to know what additional projects you rely on to create redux apps. Projects like redux-actions for example. You could write them yourself or rely on existing packages.
As a new redux user I find them confusing even though I understand they are solving a pain. Curious how you use them.
Hi, I've made a library that can handle routing and creating/updating with a remote backend. It also use a Bearer token to access routes with authentication.
I plan to add caching, built-in auth actions and pagination.
It is well documented and it should be quite straight forward using it !