fix nil pointer when context is nil #204
Merged
Conversation
This file contains 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
zeitlinger
force-pushed
the
opentracing
branch
2 times, most recently
from
83e87e5 to
cee69cf
Compare
use Params instead of AuthInfo, because that is always present respect the operationID from swagger (don't snake_case it) Signed-off-by: Gregor Zeitlinger <[email protected]>
…gci/golangci-lint-action Signed-off-by: Gregor Zeitlinger <[email protected]>
casualjim
approved these changes
Aug 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fix nil pointer when context is nil
use Params instead of AuthInfo, because that is always present
Using AuthInfo also broke DefaultAuthentication, which relied on AuthInto to be nil