Closed missinglink closed 4 years ago
cc/ @Joxit I think you're going to like this π
npm publish
+ @whosonfirst/wof@0.27.0
Yeah ! That's pretty cool ! In fact I already wrote something for exportify :sweat_smile: I can run the exportify on all files for a specific commit or all stagged files. I'm trying to rewrite the full exportify in rust but it's a pain... :sweat:
This PR contains a bunch of commands required to author this PR, these make generating patches to WOF π― times easier π
Summary:
wof fs import <dir>
takes a stream of WOF features and writes them to a filesystem, it creates the nested directory structure if required and optionally runs the WOF 'exportify' tool via docker, this makes them ready to merge upstream π±wof feature exportify
, same as above except it's streams-in & streams-out (basically just a convenient way of running 'exportify' which supports streams)wof sqlite fix <db>
command:--hierarchies
is nowfalse
by default and developers will need to explicitly specify which fixes they would like to apply--cat
flag which prints any documents which were fixed tostdout
--dryrun
flag which prevents the DB from being updated, this operation takes time so it's convenient to skip it when using the--cat
flag in some workflowsSo the cool thing about all this is that it's now possible to write a
through2
stream to update WOF records and then write them back to the repo ready for a PR!It's even possible to import them to a SQLite db and use the rest of the collection to fix integrity issues and again write it back to the filesystem ready for a PR π§
Eg: