-
-
Notifications
You must be signed in to change notification settings - Fork 70
Rewrite react-vega #613
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
base: master
Are you sure you want to change the base?
Rewrite react-vega #613
Conversation
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.
Awesome. Just a few comments but I think we are mostly good to merge and release.
Let me know when this is ready for a review. |
Ready for review 👍 @domoritz |
Please resolve the merge conflicts. Can we remove netlify then? |
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.
Thank you for the pull request! Just a few comments and then we can merge.
Will get around to addressing feedback this weekend, thanks for patience all! |
Co-authored-by: Dominik Moritz <[email protected]>
Co-authored-by: Dominik Moritz <[email protected]>
FYI I added husky back, it's just the easiest way to set up a pre-commit hook that I could find. We now run tsc, eslint, and prettier for each commit. Other than the outstanding comments that I've replied to, all other feedback should be addressed. Thanks for the patience again everybody. |
Can you resolve the merge conflicts? I am personally not a fan of precommit hooks. Let's remove them and instead add ci tests? |
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.
See my comment on ci linting
Removed husky and the pre-commit hook, updated the license, added linting in CI, and resolved merge conflicts. Let me know if there is anything else. |
#612
TODO
It's been a while since I've published a npm package so it's very possible I'm missing something as it relates to that process. Ty in advanced for any feedback you may have :) cc @domoritz @kristw