You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a few arguments that all deal with filesystem paths:
--blueprint
--datadir
--output-dir
These either have dir, -dir, or nothing special in the name. I'd like to make them predictable and my suggestion is to drop the dir and -dir parts of the names. So we get:
--blueprint
--data
--output
Thoughts? --data might be a bit terse and in general is pretty non-descriptive; perhaps --defs suits better to align with the name that seems to be the one we want in images?
--output clashes with the --output on list-images, I'd suggest renaming that one to --format.
A full command line would then look like (for example):
Demo implementation in #99 so it can be tried out to see how it feels; each change as a separate commit so they can be cherry-picked for those we like.
We have a few arguments that all deal with filesystem paths:
--blueprint
--datadir
--output-dir
These either have
dir
,-dir
, or nothing special in the name. I'd like to make them predictable and my suggestion is to drop thedir
and-dir
parts of the names. So we get:--blueprint
--data
--output
Thoughts?
--data
might be a bit terse and in general is pretty non-descriptive; perhaps--defs
suits better to align with the name that seems to be the one we want inimages
?--output
clashes with the--output
onlist-images
, I'd suggest renaming that one to--format
.A full command line would then look like (for example):
The text was updated successfully, but these errors were encountered: