Releases: loro-dev/loro
Releases · loro-dev/loro
[email protected]
[email protected]
[email protected]
Minor Changes
- be09e65: feat!: events are not async anymore
[email protected]
[email protected]
[email protected]
[email protected]
Minor Changes
-
3a0db5b: feat: add APIs to fetch values associated with the top Undo and Redo stack entries (#790)
- JS/WASM:
undo.topUndoValue()andundo.topRedoValue()return thevaluefrom the top undo/redo item (orundefinedwhen empty). - Rust:
UndoManager::{top_undo_meta, top_redo_meta, top_undo_value, top_redo_value}to inspect top-of-stack metadata and values. - Internal: stack now supports peeking the top item metadata without mutation.
This enables attaching human-readable labels via
onPush/onPopand retrieving them to keep Undo/Redo menu items up to date. - JS/WASM:
-
9a98e8d: Distinguish explicit vs implicit empty commit behavior for commit options.
- Explicit commits (user-invoked
commit()/commit_with(...)): if the transaction is empty, commit options (message/timestamp/origin) are swallowed and will NOT carry over. - Implicit commits (e.g.,
export,checkoutinternal barriers): if the transaction is empty, message/timestamp/origin are preserved for the next transaction.
Rationale: align behavior with intent. Explicit commits “finalize now”, so empty commits should not leak options. Implicit commits act as processing barriers and should not destroy user-provided options for the next real change.
Note: This refines behavior without changing the API.
- Explicit commits (user-invoked
Patch Changes
- 0fe9681: fix: handle default values for fractionalIndex and index in LoroTreeNode
[email protected]
Minor Changes
- 8c898ee: Perf: faster snapshot import speed
[email protected]
[email protected]
Patch Changes
- ec95b50: Fix local event error