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
Whenever gateway is applied, it's responsibility of the package user to identify on which endpoints it should run, but it would be much nicer to be able to use route matching there, like this:
# No method means all methodsmutate_request"/plans/:id"doend# Only for GET requestsmutate_request:get,"/plans"doendmutate_response"/plans/:id"doendmutate_response:get,"/plans"doend
Additional benefit is that gate would be self-documenting in a way that it's easy to see all changes per endpoint and even to generate simple changelog for them.
TODO:
Do not forget to add new macros to .formatter.exs so that they won't be wrapped in brackets.
The text was updated successfully, but these errors were encountered:
Whenever gateway is applied, it's responsibility of the package user to identify on which endpoints it should run, but it would be much nicer to be able to use route matching there, like this:
Additional benefit is that gate would be self-documenting in a way that it's easy to see all changes per endpoint and even to generate simple changelog for them.
TODO:
.formatter.exs
so that they won't be wrapped in brackets.The text was updated successfully, but these errors were encountered: