feat(ama-sdk-create): allow creation without a scope #1474
Merged
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.
Proposed change
When running
npm create @ama-sdk typescript my-package
, I would intuitively expect amy-package
package to be created inmy-package
folder.What currently happens is the creation of the
@sdk/my-package
package inside thesdk/my-package
folder. Why is thissdk
scope added? I suggest in this PR to remove thesdk
default scope.