automerge/javascript/test
Alex Good de16adbcc5 Explicity create empty changes
Transactions with no ops in them are generally undesirable. They take up
space in the change log but do nothing else. They are not useless
though, it may occasionally be necessary to create an empty change in
order to list all the current heads of the document as dependents of the
empty change.

The current API makes no distinction between empty changes and non-empty
changes. If the user calls `Transaction::commit` a change is created
regardless of whether there are ops to commit. To provide a more useful
API modify `commit` so that if there is a no-op transaction then no
changes are created, but provide explicit methods to create an empty
change via `Transaction::empty_change`, `Automerge::empty_change` and
`Autocommit::empty_change`. Also make these APIs available in Javascript
and C.
2022-12-02 12:12:54 +00:00
..
legacy Move wrappers/javascript -> javascript 2022-10-16 19:55:54 +01:00
basic_test.ts Explicity create empty changes 2022-12-02 12:12:54 +00:00
columnar_test.ts Move wrappers/javascript -> javascript 2022-10-16 19:55:54 +01:00
extra_api_tests.ts Move wrappers/javascript -> javascript 2022-10-16 19:55:54 +01:00
helpers.ts Move wrappers/javascript -> javascript 2022-10-16 19:55:54 +01:00
legacy_tests.ts js: Add Automerge.clone(_, heads) and Automerge.view 2022-10-26 14:01:11 +01:00
sync_test.ts Move wrappers/javascript -> javascript 2022-10-16 19:55:54 +01:00
text_test.ts Move wrappers/javascript -> javascript 2022-10-16 19:55:54 +01:00
uuid_test.ts Move wrappers/javascript -> javascript 2022-10-16 19:55:54 +01:00