Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

redux-orm

Package Overview
Dependencies
Maintainers
3
Versions
70
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

redux-orm - npm Package Versions

1
7

0.9.0-rc.3

Diff

tommikaikkonen
published 0.9.0-rc.2 •

tommikaikkonen
published 0.9.0-rc.1 •

tommikaikkonen
published 0.9.0-rc.0 •

tommikaikkonen
published 0.8.4 •

Changelog

Source

0.8.4

Adds UMD build to partially fix #41. You can now use or try out redux-orm through a script tag:

<script src="https://unpkg.com/redux-orm/dist/redux-orm.min.js"></script>

redux-orm.js will point to the master version of the library; If you need to stick to a version, make a copy or build it yourself.

tommikaikkonen
published 0.8.3 •

Changelog

Source

0.8.3

Fixed bug that mutated the backend options in Model if you supplied custom ones, see Issue 37. Thanks to @diffcunha for the fix!

tommikaikkonen
published 0.8.2 •

tommikaikkonen
published 0.8.1 •

Changelog

Source

0.8.1

Added babel-runtime to dependencies

tommikaikkonen
published 0.8.0 •

Changelog

Source

0.8.0

Adds batched mutations. This is a big performance improvement. Previously adding 10,000 objects would take 15s, now it takes about 0.5s. Batched mutations are implemented using immutable-ops internally.

Breaking changes:

  • Removed indexById option from Backend. This means that data will always be stored in both an array of id's and a map of id => entity, which was the default setting. If you didn't explicitly set indexById to false, you don't need to change anything.
  • Batched mutations brought some internal changes. If you had custom Backend or Session classes, or have overridden Model.getNextState, please check out the diff.
tommikaikkonen
published 0.7.0 •

Changelog

Source

0.7.0

Breaking changes:

Model classes that you access in reducers and selectors are now session-specific. Previously the user-defined Model class reference was used for sessions, with a private session property changing based on the most recently created session. Now Model classes are given a unique dummy subclass for each session. The subclass will be bound to that specific session. This allows multiple sessions to be used at the same time.

You most likely don't need to change anything. The documentation was written with this feature in mind from the start. As long as you've used the model class references given to you in reducers and selectors as arguments (not the reference to the model class you defined), you're fine.

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc