loro/crates/loro-wasm/CHANGELOG.md

Changelog

0.16.4-alpha.0

Patch Changes

• Export/import JSON schema

0.16.3

Patch Changes

• 6d47015: Make cursors transformation better in undo/redo loop
• dc55055: Perf(wasm) cache text.toDelta

0.16.2

Patch Changes

• 34f6064: Better undo events & transform cursors by undo manager (#369)

  🧪 Testing

  • Enable compatibility test (#367)

0.16.1

Patch Changes

• 5cd80b0: Refine undo impl

  • Add "undo" origin for undo and redo event
  • Allow users to skip certain local operations
  • Skip undo/redo ops that are not visible to users
  • Add returned bool value to indicate whether undo/redo is executed

0.16.0

Minor Changes

• c12c2b9: Movable Tree Children & Undo

  🐛 Bug Fixes

  • Refine error message on corrupted data (#356)
  • Add MovableList to CONTAINER_TYPES (#359)
  • Better jitter for fractional index (#360)

  🧪 Testing

  • Add compatibility tests (#357)

  Feat

  • Make the encoding format forward and backward compatible (#329)
  • Undo (#361)
  • Use fractional index to order the children of the tree (#298)

  🐛 Bug Fixes

  • Tree fuzz sort value (#351)
  • Upgrade wasm-bindgen to fix str free err (#353)

0.15.3

Patch Changes

• 43506cc: Fix unsound issue caused by wasm-bindgen

  🐛 Bug Fixes

  • Fix potential movable list bug (#354)
  • Tree fuzz sort value (#351)
  • Upgrade wasm-bindgen to fix str free err (#353)

  📚 Documentation

  • Simplify readme (#352)

0.15.2

Patch Changes

• e30678d: Perf: fix deletions merge

  🐛 Bug Fixes

  • (wasm) Movable list .kind() (#342)

  ⚡ Performance

  • Delete span merge err (#348)

  ⚙️ Miscellaneous Tasks

  • Warn missing debug impl (#347)

0.15.1

Patch Changes

• 04c6290: Bug fixes and improvements.

  🐛 Bug Fixes

  • Impl a few unimplemented! for movable tree (#335)
  • Refine ts type; reject invalid operations (#334)
  • Get cursor err on text and movable list (#337)
  • Missing MovableList in all container type (#343)
  • Upgrade generic-btree to allow large btree (#344)

  📚 Documentation

  • Add warn(missing_docs) to loro and loro-wasm (#339)
  • Minor fix on set_change_merge_interval api (#341)

  ⚙️ Miscellaneous Tasks

  • Skip the checking if not debug_assertions (#340)

0.15.0

Minor Changes

• 35b9b6e: Movable List (#293)

  Loro's List supports insert and delete operations but lacks built-in methods for set and move. To simulate set and move, developers might combine delete and insert. However, this approach can lead to issues during concurrent operations on the same element, often resulting in duplicate entries upon merging.

  For instance, consider a list [0, 1, 2]. If user A moves the element '0' to position 1, while user B moves it to position 2, the ideal merged outcome should be either [1, 0, 2] or [1, 2, 0]. However, using the delete-insert method to simulate a move results in [1, 0, 2, 0], as both users delete '0' from its original position and insert it independently at new positions.

  To address this, we introduce a MovableList container. This new container type directly supports move and set operations, aligning more closely with user expectations and preventing the issues associated with simulated moves.

  Example

  import { Loro } from "loro-crdt";
  import { expect } from "vitest";
  
  const doc = new Loro();
  const list = doc.getMovableList("list");
  list.push("a");
  list.push("b");
  list.push("c");
  expect(list.toArray()).toEqual(["a", "b", "c"]);
  list.set(2, "d");
  list.move(0, 1);
  const doc2 = new Loro();
  const list2 = doc2.getMovableList("list");
  expect(list2.length).toBe(0);
  doc2.import(doc.exportFrom());
  expect(list2.length).toBe(3);
  expect(list2.get(0)).toBe("b");
  expect(list2.get(1)).toBe("a");
  expect(list2.get(2)).toBe("d");
  

0.14.6

Patch Changes

• 24cf9b9: Bug Fix

  🐛 Bug Fixes

  • Attached container can be inserted to Map or List (#331)

0.14.5

Patch Changes

• 73e3ba5: Bug Fix

  🐛 Bug Fixes

  • (js) Allow convert from undefined to LoroValue (#323)

  🚜 Refactor

  • Refine ts type (#322)

0.14.4

Patch Changes

• 598d97e: ### 🚜 Refactor

  • Refine the TS Type of Awareness
  • Parse Uint8array to LoroValue::Binary (#320)

  📚 Documentation

  • Update how to publish new npm pkgs

0.14.3

Patch Changes

• a1fc2e3: Feat: Awareness (#318)

0.14.2

Patch Changes

• Refactor rename StablePosition to Cursor

  • Rename stable pos to cursor (#317)

0.14.1

Patch Changes

• Supports Cursors

  🚀 Features

  • Cursors (#290)

0.14.0

Minor Changes

• Improved API

  🚀 Features

  • Access value/container by path (#308)
  • Decode import blob meta (#307)

  🐛 Bug Fixes

  • Decode iter return result by updating columnar to 0.3.4 (#309)

  🚜 Refactor

  • Replace "local" and "fromCheckout" in event with "triggeredBy" (#312)
  • Add concrete type for each different container (#313)
  • (ts) Make types better (#315)

  📚 Documentation

  • Refine wasm docs (#304)
  • Clarify that peer id should be convertible to a u64 (#306)

  ⚙️ Miscellaneous Tasks

  • Add coverage report cli (#311)

0.13.1

Patch Changes

• Fix type errors and conversion from js->rust error

0.13.0

Minor Changes

• BREAKING CHANGE: detached mode for Containers #300

  Now creating sub-containers is much easier.

  A container can be either attached to a document or detached. When it's detached, its history/state is not persisted. You can attach a container to a document by inserting it into an existing attached container. Once a container is attached, its state, along with all of its descendants's states, will be recreated in the document. After attaching, the container and its descendants will each have their corresponding "attached" version of themselves.

  When a detached container x is attached to a document, you can use x.getAttached() to obtain the corresponding attached container.

  When we use const text = new LoroList(), it's not attached to a doc. But we can insert it into a doc by map.insertContainer(”t”, text), where the map is attached. But if we want the operations on the text to be recorded to the doc, we now need to get its attached version. So we can use “let attachedText = text.getAttached()”

0.12.0

Minor Changes

• Add getParent and getOrCreate

0.11.1

Patch Changes

• Fix batch import

0.11.0

Minor Changes

• Fix a few bugs and include BREAKING CHANG refactors

  • fix: should not reset the state when calling checkout to latest (#265)
  • refactor: only send a event for one import/transaction/checkout (#263)
  • perf: optimize snapshot encoding speed (#264)
  • feat: remove deleted set in tree state and optimize api (#259)

0.10.1

Patch Changes

• fix: remove checking after checkout

0.10.0

Minor Changes

• New encoding schema
  • BREAKING CHANGE: refactor: Optimizing Encoding Representation for Child Container Creation to Reduce Document Size (#247)
  • feat: compare frontiers causal order (#257)
  • docs: update docs about rich text style (#258)

0.9.4

Patch Changes

• Fix a few richtext time travel issues

0.9.3

Patch Changes

• feat: add getChangeAtLamport

0.9.2

Patch Changes

• Fix a few rich text issue
  • fix: time travel back should be able to nullify rich text span (#254)
  • fix: formalize apply delta method (#252)
  • fix: how to find best insert pos for richtext & expand type reverse behavior (#250)

0.9.1

Patch Changes

• Fix use consistnt peer id repr and expose VersionVector type

0.9.0

Minor Changes

• Refine the rich text CRDT in Loro

0.8.0

Minor Changes

• Stabilize encoding and fix several issues related to time travel

0.7.2-alpha.4

Patch Changes

• Fix encoding value err

0.7.2-alpha.3

Patch Changes

• Fix export compressed snapshot

0.7.2-alpha.2

Patch Changes

• Add compressed method

0.7.2-alpha.1

Patch Changes

• Fix v0 exports

0.7.2-alpha.0

Patch Changes

• Add experimental encode methods

0.7.1

Patch Changes

• Fix a few richtext errors

0.7.0

Minor Changes

• refactor: remove setPanicHook and call it internally when loaded

0.6.5

Patch Changes

• Fix checkout err on seq data

0.6.4

Patch Changes

• Fix time travel issue #211

0.6.1

Patch Changes

• 6753c2f: Refine loro-crdt api

0.6.0

Minor Changes

• Improve API of event

All notable changes to this project will be documented in this file. See standard-version for commit guidelines.