Andrey Sitnik
Andrey Sitnik
Vite `node_modules` footprint is smaller and performance is better.
```js useFilter(Task, { projectId }, { pagination: { page: 1, perPage: 50 } }); ``` Just flexible API on first iteration. Let’s users will implement it.
It could be hard to compare values like `100:uImkcF4z` or `1487805099387 server:FnXaqDxY 0`. If we generate some sort of color has for them, it will be easier to compare them.
It will be nice to have API like: ```js let answer = await store.dispatch.sync(action) answer => Action[] ``` On the server we can have something like: ```js async process (ctx)...
CRA maintenance is very bad and it still does not support dual ESM/CJS packages. We should move to another boilerplate.
We need an example how to integrate the Logux server with the REST backend
`httpOnly` cookie generation will be a good example for custom HTTP endpoint in the Logux server.
- [ ] Add Logux State to Parts - [ ] Add Logux State to Starting Project - [ ] Hide Redux / Vuex from menu or delete from docs...
- [x] Release Logux Django - [x] Add Django snippets to docs @egregors https://github.com/logux/docs/pull/68 - [ ] Add Django API @ai https://github.com/logux/django/issues/23
Right now Logux Server process all actions “in parallel” (on one thread, just in async “parallel”). It could cause a problem when actions are related: 1. Client A created post...