v1.0.2
We introduce breaking changes after the major semver update (is there a 3 second rule for packages that don't have a lot of inward dependencies on npm ? :) )
The breaking changes should however in general allow to keep data that would otherwise be deleted or overwritten. So unless your code relies heavily on aggressive deletes (such as recursive deletes of blank nodes), then you should be fine!
If you do rely on past behavior then using overwrite:true and cut:true will recover most of the functionality except a couple of backward compatibility breaking changes which are generally about leaving alone existing data (see put tests marked with break compatibility for details).
Breaking Changes
'put'and'del'methods are more conservative by default.- Cannot pass an IRI string to
'del'. (except with thecutoptions)
Added
'cut'method modelled loosely on LDPatch which deletes blank nodes.recurseoption tocut( anddelwithcut: true) which recursively deletes triples (including blank nodes) mentioned in the document or starting at the IRI.
Fixes
- del() cannot accept strings, but put() can #50
- del() empties entire storage #49
- Set preserve to true by default #51
- Graph "scrubbing" is too agressive #45
Known Bugs
- Setting "@context" as a string timeout (waiting for an upstream fix). #47
- Deleting blank nodes by ids is not yet possible. Design discussion at #42
Thanks a lot to @mcollina for the handover and @BigBlueHat for the bug reports and the work on the new LevelGraph Playground!