-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added the CLI package #11
Conversation
7c46643
to
e0e7ef0
Compare
e0e7ef0
to
d485424
Compare
87bcfe4
to
7fbec8b
Compare
7fbec8b
to
88a30fc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome, I'm excited to use this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need some explanation for the change in naming patterns. We want to be consistent so if we're going to recommend _
then we should probably match that in our source as well. That said, I haven't seen anyone use this pattern. Most libraries/frameworks use .
so I'd like to understand the reasoning for this change better.
Pull Request
π Description
Added the CLI package which will install the default package.
π« Issues
Closes #3
β Checklist
General
β Next Steps