-
Notifications
You must be signed in to change notification settings - Fork 117
fix: define properly query parameters #660
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
Conversation
PR Reviewer Guide 🔍(Review updated until commit 704ed7b)Here are some key observations to aid the review process:
|
PR Code Suggestions ✨Explore these optional code suggestions:
|
Persistent review updated to latest commit 704ed7b |
PR Code Suggestions ✨No code suggestions found for the PR. |
PR Type
Bug fix, Enhancement
Description
Fix handling of
allowedRoles
andmetadata
query parameters.Update OpenAPI spec for correct query parameter definitions.
Parse
metadata
as JSON-encoded string in API handler.Update tests to use JSON string for
metadata
.Changes diagram
Changes walkthrough 📝
openapi.yaml
Update OpenAPI spec for allowedRoles and metadata query params
docs/openapi.yaml
style: form
andexplode: false
forallowedRoles
.metadata
to a JSON-encoded string in query parameters.metadata
description and schema to reflect JSON encoding.server.gen.go
Fix and parse allowedRoles/metadata query parameters in handler
go/api/server.gen.go
allowedRoles
to not require parameter and not explode.metadata
query param as JSON string and unmarshal into map.metadata
JSON.types.gen.go
Clarify Metadata field as JSON-encoded string
go/api/types.gen.go
Metadata
field comment to specify JSON-encoded string.sign_in_provider_test.go
Update test to use JSON string for metadata param
go/controller/sign_in_provider_test.go
metadata
as JSON string.