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
We're discussing some way to handle headers, but we need to be careful when having any data beyond payload in service API, mostly because of future schema validations possibilities.
We're discusisng ability to have metadata abstraction that would use headers under the hood and clearly inform users that it will not be part of any validations.
Proposed change
Unless I've missed it I don't see anyway for a service's endpoint to
respond()
whilst supplying headers (other than in the Error case, that is).Use case
Add a
respond_with_headers()
method following the pattern set byrequest_with_headers()
andpublish_with_headers()
.Contribution
No response
The text was updated successfully, but these errors were encountered: