Skip to content

Releases: alexvcasillas/react-mobx-router

Version 0.2.2

05 Mar 13:05
Compare
Choose a tag to compare

Updated all depencendies to its latets.

Version 0.2.1

01 Jun 08:25
Compare
Choose a tag to compare

This release has the following features:

  • Improvements on performance.
  • UI Improvements.
  • React Scripts 1.0.7.
  • Styled Components v2.0.0.
  • Upgraded various dependencies to their latest version.
  • Example of Asynchronous Fetching from Github upgraded and improved UX/UI.

Hope ya'll enjoy and hope to also hear feedback from you!

Version 0.2.0

09 May 06:29
Compare
Choose a tag to compare

This release comes with the first production example built with 3RMXi.

This release contains:

  • Decoupled UI from the state of the App. All components are Stateless.
  • Styled-Components implemented and glued together with the project (but easily removable).
  • Asynchronous Fetching Example with MobX Stores.

As this version contains new features added like the ones described above (eg: styled-components) and an example to demonstrate the use of this boilerplate a MINOR version is released so we change to 0.2.0 instead of 0.1.4.

You can also check a live demo of the example here: https://react-git-app.firebaseapp.com/

Version 0.1.3a

27 Apr 12:43
Compare
Choose a tag to compare

Improved components making all of them stateless.
Now all the component's state handling depends on @mobxjs so everything is much more efficient and amazing.

This release contains all the recent hotfixes.

Version 0.1.3

27 Apr 11:12
Compare
Choose a tag to compare

Improved components making all of them stateless.
Now all the component's state handling depends on @mobxjs so everything is much more efficient and amazing.

Version 0.1.2

25 Apr 19:30
Compare
Choose a tag to compare

At this point #3RMXi is production ready. It will always could be improved but this version is valid for production purposes.

This version had decoupled the State from the UI in the <Language /> component so now we don't depend on state changing and just letting MobX handle the state apart from the UI so we can gain some performance benefits in terms of freeing the <Language />component from having to handle it's own state when we already had a Store with computed and observable values that could handle this in a much better way than the component state itself.