strikersoft/poa

Opinionated React framework

poa's Issues

Add bootstraping component rendering when awaiting on @@INIT_ACTION

Provide own http client (based on axios) and inject to side-effects

Add examples with CRA, CRA-TS, Real world

Configure logger to use debug in development and only error's in production mode. Add export the instance to user

Improve README.md

• Add description of framework
• Add examples
• Add install instructions
• Add API description

More ?

Refactor all Jasmine to Jest

Refactor all Jasmine tests from Satchel to Jest

Ensure sideEffects executed always after mutators

Re-export mobx, react-router, i18next internals to users

Add ability to pass middleware into boot function

Export mobx APIs from POA

add API to get current language

Allow `createAction` without payload

Provide built-in logging middleware in dev mode

NavLink should warn in dev mode when route is not matched

Same behaviour as

Migrate from react-router v4

So now, we use react-router v4 (react-router-dom) and some simple abstraction on top of it.

However, there is a tons of disadvantages:

• react-router does not relate on observables and have their own events system
• react-router can't be defined statically via some config
• react-router does not have idiomatic way of doing data fetching, guarding, etc..

Preferred way is to migrate to https://github.com/mobx-little-router/mobx-little-router or create our own

Introduce built-in option for Sentry. Configure to send on error log and send last action and user store.

Improve code coverage to 95%

Inject logger into, sideEffects and Router+Components

Improve auto-generated documentation

• Branding
• Show only public APIs

More ?

Introduce project logo