-
Notifications
You must be signed in to change notification settings - Fork 3
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
Unit tests for personalAccessKey utils #53
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.
LGTM! Two small comments
types/Accounts.ts
Outdated
// personalaccesskey = 'personalaccesskey', | ||
// apikey = 'apikey', | ||
// oauth2 = 'oauth2', | ||
// } |
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.
Did you mean to leave this in?
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.
Nope, good catch
package.json
Outdated
@@ -25,7 +25,7 @@ | |||
"release:major": "yarn check-main && yarn version --major && yarn build && yarn pub && yarn push", | |||
"release:minor": "yarn check-main && yarn version --minor && yarn build && yarn pub && yarn push", | |||
"release:patch": "yarn check-main && yarn version --patch && yarn build && yarn pub && yarn push", | |||
"test": "jest --silent" | |||
"test": "jest" |
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.
Just curious why you're removing this here. With it off, every console.log
and console.debug
gets triggered which I found a little distracting. Was there anything important that was getting skipped over?
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.
Also noticed you changed this in your other PR so might end up with a conflict
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.
I took this out because it made debugging the tests really difficult. I was trying to console log and wasn't seeing any of the output. I figured that we can manually run with yarn run test --silent
if the output gets annoying. After playing around with it for a while though, the console logs didn't bother me.
Description and Context
Copying unit tests from cli-lib for personalAccessKey.
Screenshots
TODO
Who to Notify