Add buffrs new command to init a package in a non-existing folder
#256
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gbouv
force-pushed
the
gbouv/add-new-command
branch
from
0b71b8c
to
57164bc
Compare
mara-schulke
reviewed
Jul 4, 2024
gbouv
force-pushed
the
gbouv/add-new-command
branch
from
a74d07b
to
ec1ea68
Compare
mara-schulke
approved these changes
Jul 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #185
The new
buffrs newcommand takes the--libor--apiflag similarly toinitand a mandatorypackageNameparameter. In the current working directory (where the CLI is invoked) creates a directory named<packageName>and initialize it with theProto.tomlfile andprotofolder.If a directory
<packageName>already exists in the current working directory, the command fails.