v0.4.0
·
2475 commits
to master
since this release
Overview
0.4.0 adds basic support for resolving merge conflicts, imports from postgres databases, and a variety of other minor features
Major changes in this release
- Basic conflict resolution:
- Major improvements to
sno import
andsno init --import
: - Added
sno show
: shows a commit. With-o json
generates a patch (#48) - Added
sno apply
to apply the patches generated bysno show -o json
(#61)
Minor features / fixes:
- add a changelog (here!)
sno import
enhancements (in addition to major changes above):- GPKG database paths no longer need
GPKG:
prefix - now takes table names as separate arguments
- Added
--primary-key=FIELD
to override primary key field name - Added
--message
to customize the commit message --list
no longer requires a repository
- GPKG database paths no longer need
sno init --import
enhancements:- imports are much faster (#55)
- now imports all tables from database, doesn't allow table to be specified
- Many JSON output improvements:
- JSON output is specified with
-o json
instead of--json
(#98) - Added syntax highlighting to JSON output when viewed in a terminal (#54)
sno diff
JSON output layout has changed - features are now flat objects instead of GeoJSON objects. This is much more compact (#71)- Added JSON output option for most commands
- Added
--json-style
option to several commands to control JSON formatting (#70)
- JSON output is specified with
sno diff
:sno commit
:- can now commit some subset of the changes by supplying filter args, ie
[dataset[:pk]]
(#69)
- can now commit some subset of the changes by supplying filter args, ie
- removed
import-gpkg
command; useimport
instead (#85) - Error messages now go to stderr instead of stdout (#57)
- Error conditions now use exit codes to indicate different types of errors (#46)
Compatibility
Repositories created with Sno v0.2 onwards are compatible with v0.4. For assistance upgrading any v0.1 repositories, please read our upgrade guide.