You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I'm writing the integration test for #83, I ran into PUT calls returning HTTP 405, which seems reasonable because the code never registers routes for PUT and only does so for PATCH. However, the API documentation specifies that every every route accepting PATCH also accepts PUT.
We can:
Removing references of PUT in the documentation
Add support for PUT
Either of those solutions wouldn't be a breaking change. Which one is preferred?
As I'm writing the integration test for #83, I ran into PUT calls returning HTTP 405, which seems reasonable because the code never registers routes for PUT and only does so for PATCH. However, the API documentation specifies that every every route accepting PATCH also accepts PUT.
We can:
Either of those solutions wouldn't be a breaking change. Which one is preferred?
Here are the relevant files segments.
authn-server/server/private_routes.go
Lines 14 to 58 in 7f82ad8
authn-server/lib/route/route.go
Lines 15 to 40 in 7f82ad8
The text was updated successfully, but these errors were encountered: