Instead of using ThunkDispatch<AppState, {}, AnyAction> and needing 3 imports, we can declare our own types CKDispatch and be consistent and resilient to future library (as redux-promise for example) dependencies.

As states the official doc:

We recommend always using the “object shorthand” form of mapDispatchToProps, unless you have a specific reason to customize the dispatching behavior.

From Official react-redux documentation

So, we should use the "object shorthand" as much as possible.

Add spinner graphic when loading parts.

Steps to reproduce:

• Login
• Refresh

You are not logged in anymore
(More, even the main list do not load)

When working with redux, we should always use selectors...

listId will be other values than 1

Manage forms is a complex subject.
Using redux-form will facilitate the whole process.

Here the link to follow:
https://medium.com/@martin_hotell/10-typescript-pro-tips-patterns-with-or-without-react-5799488d6680

Keep a consistent glossary to describe common model objects.

Seen in 0.3.0

Seen in 0.3.0

As a regular user,
I want to select a preferred list,
To be able to see it in the dashboard

For using with each client request, we need a token from the redux store, the path is more or less complicated, a selector is suitable here.

As a user,
I want to have multiple projects,
To be able to split my tasks

Since 0.3.0 (and front framework change), the profile page was not reimplemented.

Each request, a new token is sent, we should save it each time.