Skip to content
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

No way to respond() with headers #1355

Open
antskelton42 opened this issue Dec 30, 2024 · 1 comment
Open

No way to respond() with headers #1355

antskelton42 opened this issue Dec 30, 2024 · 1 comment
Labels
proposal Enhancement idea or proposal

Comments

@antskelton42
Copy link

antskelton42 commented Dec 30, 2024

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 by request_with_headers() and publish_with_headers().

Contribution

No response

@antskelton42 antskelton42 added the proposal Enhancement idea or proposal label Dec 30, 2024
@Jarema
Copy link
Member

Jarema commented Dec 31, 2024

It was a design decision.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Enhancement idea or proposal
Projects
None yet
Development

No branches or pull requests

3 participants
@Jarema @antskelton42 and others