atom.io@0.25.4

Patch Changes

• 434e6d4: 🐛 Fixed bug in AtomIO's core that would occur in situations where a package manager like pnpm installed multiple AtomIO instances for purposes of version safety/intercompatibility. This could lead to different IMPLICIT.STOREs being used on adjacent lines, and as a result, bizarre errors would be thrown. Resolved this by making the IMPLICIT.STORE discoverable on globalThis.

atom.io@0.25.3

Patch Changes

• a6283c4: 🐛 Fix bug where, when using useO in ephemeral stores, a state would not be created as needed in React components.

atom.io@0.25.2

Patch Changes

• a9da731: 🐛 Fix bug where, GetterToolkit's and SetterToolkit's get method would error when retrieving state from a family that wasn't an AtomFamily.

atom.io@0.25.1

Patch Changes

• 166625e: 🐛 Fixed bug where, when attempting to retrive states with CtorToolkit["get"], the states would be fail to be found.
• 166625e: 🐛 Fixed bug where, when a molecule could not be found, its key would not be properly error-logged.

atom.io@0.25.0

Minor Changes

• a308896: 💥 BREAKING CHANGE: The method join from MoleculeToolkit has been absorbed into the bond method; it now returns tokens for the relations of the entity bonded to the join in question.

• 3c495a7: 🎨 All attributes and types called Transactors have been renamed Toolkit to reflect the broader role of this pattern in selector evaluations and molecule constructors.

• 091c5de: ✨ getState and setState can now be used for family members without requiring findState. Simply pass the family member and key.

  const countAtoms = atomFamily<number, string>({
    key: `count`,
    default: 0,
  });
  
  getState(countAtoms, `find-me`); // -> 0
  setState(countAtoms, `find-me`, 1);
  getState(countAtoms, `find-me`); // -> 1

  ⚠️ Note that, if the family member is not found, this will throw a NotFoundError in immortal stores.

Patch Changes

• 091c5de: 🐛 Fixed bug where, when creating a new Store, unless that store was copied from an existing store, its configuration options would not be set.
• 091c5de: ✨ Silo receives the disposeState method.

atom.io@0.24.8

Patch Changes

• cf66736: 🚀 Greatly improve performance for selectors with deep dependency trees. Redundant work is now avoided when discovering a selector's root atoms.

atom.io@0.24.7

Patch Changes

• e4d32db: 🐛 Fixed bug where, when getting a molecule in a selector, the get operation would throw.

atom.io@0.24.6

Patch Changes

• 44a1d5a: 🐛 Fixed a bug where, when setting a selector in a transaction, that selector would leak to the outer store.
• 44a1d5a: 🐛 Fixed a bug where, when creating a molecule in a transaction, the molecule creation event wouldn't be nested into the transaction update.
• 44a1d5a: 🐛 Fixed a bug where, when creating a molecule which bonds atoms, the atom creations would be redundantly captured on transactions/timelines, leading to noisy warnings in the console.

atom.io@0.24.5

Patch Changes

• 84a0737: 🐛 Fixed an issue where, when applying a transaction in which a mutable atom was created, atom.io would attempt to re-create that atom twice, which led to a pesky error log.

atom.io@0.24.4

Patch Changes

• 6ab042e: ✨ The join function from MoleculeTransactors now returns the original join for convenience.