More detailed API key error #921
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gracegoo-stripe
approved these changes
Jul 25, 2022
mnorth-stripe
requested changes
Jul 26, 2022
mnorth-stripe
left a comment
mnorth-stripe
left a comment
There was a problem hiding this comment.
Thanks for making our CLI errors more actionable!
I think you could add one more assertion to the test and then it's ready to ship
Collaborator
|
Closing this, very old |
mnorth-stripe
left a comment
mnorth-stripe
left a comment
There was a problem hiding this comment.
Closing this PR -- some tooling was getting stuck
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Noticed that we were swallowing config errors when returning API keys if something on the config-level was busted. We probably want that for general usage but I made this configurable depending on the log-level.