-
Notifications
You must be signed in to change notification settings - Fork 7
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
Commander cli #47
Commander cli #47
Conversation
Pull Request Test Coverage Report for Build 9608043343Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9636137265Details
💛 - Coveralls |
memory-viz/src/tests/cli.spec.tsx
Outdated
it("produces consistent svg when provided height and width options", (done) => { | ||
fs.writeFileSync(filePath, input); | ||
|
||
exec(`memory-viz ${filePath} --height=700, width=1200`, (err) => { |
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.
There shouldn't be a comma after the 700
package.json
Outdated
@@ -17,5 +17,8 @@ | |||
}, | |||
"lint-staged": { | |||
"**/*": "prettier --write --ignore-unknown" | |||
}, | |||
"dependencies": { |
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 isn't the right place to add this; you need to add it to the memory-viz/
subpackage.
I actually realized that this is also true for the tmp
dev dependency for testing. Please go ahead and fix that in this PR (i.e., remove tmp
from the dev dependency list above and move it to the memory-viz/
subpackage.
Pull Request Test Coverage Report for Build 9640526770Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9647281387Details
💛 - Coveralls |
Proposed Changes
Adopted
Commander.js
library for the MemoryViz CLI, and added optional--width
and--height
arguments to specify the width and height of SVGs generated with the CLI. This simplifies the CLI code and adds functionality....
Type of Change
(Write an
X
or a brief description next to the type or types that best describe your changes.)Checklist
(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the
[ ]
into a[x]
in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)Before opening your pull request:
After opening your pull request:
Questions and Comments
(Include any questions or comments you have regarding your changes.)