fix: Better CORS handling #61
Closed
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
This inject cors as option using `WithCors` and also fix the usage because before of this cors were not applied to server.
EwenQuim
reviewed
Mar 4, 2024
| @@ -11,6 +11,7 @@ import ( | |||
|
|
|||
| "github.com/getkin/kin-openapi/openapi3" | |||
| "github.com/golang-jwt/jwt/v5" | |||
| "github.com/rs/cors" | |||
| ) | |||
There was a problem hiding this comment.
rs/cors is a middleware, I don't want to add it to fuego : users should be free to chose the middlewares they want (some users don't need cors)
|
Thanks for the work and sorry to close this pull request! |
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.
This inject cors as option using
WithCorsand also fix the usagebecause before of this cors were not applied to server.
Fixes: #59