[Suggestion] Handling relative path when initiating component #941
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.
Not creating an issue - just a small PR that allows using relative path when initiating new component.
Why this change?
In our team all the components are in
/src/components
directory. All the grunt/npm tasks are defined at the top level though. When we want to create a new component it requires us to first go two levels down to do theinit
and then go back up to run registry locally or run the tests.Supporting relative path would allow us to slightly reduce number of steps during the development process.
This change affects only init CLI.
Test plan (required)
Output when running

node src/cli/ init test-components/hello-test