Consider nesting magic commands under run
#27
Comments
|
This is going to be a breaking change, but I think it's better to get it out of the way now that regret it in six months. |
ianwremmel
added a commit
that referenced
this issue
Mar 28, 2018
At some point, the original "magic" implementation was likely to lead to a conflict between a consumer script and a clark native method. Now, all generated scripts will be namespaced under "clark run" (just like "npm run") to avoid such collisions" Fixes #27
|
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
ianwremmel
added a commit
that referenced
this issue
Jan 9, 2020
BREAKING CHANGE: At some point, the original "magic" implementation was likely to lead to a conflict between a consumer script and a clark native method. Now, all generated scripts will be namespaced under "clark run" (just like "npm run") to avoid such collisions" Fixes #27
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Magic commands are nice, but could collide with a future built-in command.
The text was updated successfully, but these errors were encountered: