-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ick should not change the database name #5
Comments
CristianCantoro
changed the title
ick should change the database name
ick should not change the database name
Jan 23, 2021
CristianCantoro
added a commit
to CristianCantoro/integrity-checker
that referenced
this issue
Jan 23, 2021
I agree with this, happy to take the PR when it's passing. |
CristianCantoro
added a commit
to CristianCantoro/integrity-checker
that referenced
this issue
Jan 27, 2021
elliottslaughter
pushed a commit
that referenced
this issue
Jan 28, 2021
Fixed by #6. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am splitting this from issue #2, as pointed out there the fact that
ics
automatically sets the extensions to.json.gz
is confusing. In particular:$ ick build datadb data
, produces a db file calleddatadb.json.gz
.$ ick build datadb.foo data
, still produces a db file calleddatadb.json.gz
.$ ick build datadb.foo.bar data
, produces a db file calleddatadb.foo.json.gz
.As suggest above,
ick
should not change the name of the db as passed from the CLI.The text was updated successfully, but these errors were encountered: