Move build and update commands to the core #8
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.
Move
build:*
andupdate:*
command placeholders to theeas-cli
core package. Removewebhook:*
placeholders.Why?
Plugins are a useful feature of
oclif
, they can be used to create extensions to the CLI that can be installed separately even if they're not a part of the default installation and to even share commands between many CLIs. They're also a way to split a CLI into modular components.However, build and update commands should be in the core package and not be separate plugins (at least for the time being), because:
tsc
.@eas/config
for functionality that's shared between packages.I'm also removing the
webhook:*
command stubs for now. I added them as examples initially, but currently I'm not certain, if we need to have these commands for editing webhooks, as a website UI seems like a better experience for this task.