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
Response has a series of utility methods for setting complex headers, like Set-Cookie or Link.
It would be nice to have a similar ability also in the HttpStatus and in the HttpError.
While ideally the interface could be duplicated/shared in a common superclass, I think that most of the benefits could be achieved by making the _wsgi_headers and _asgi_headers public and setting the headers of the HttpStatus/HttpError to that value.
CaselIT
changed the title
Provide a way of using Resource header functions from HttpStatus and HttpError
Provide a way of using Response header functions from HttpStatus and HttpError
Aug 29, 2020
Hi @G-Sheridan !
And thanks for sharing. Sounds like a cool AI/DL project to tinker with!
That being said, I'm afraid this issue falls into the remaining gap towards 1.00 AUC, and towards artificial general intelligence.
Despite a really well written description by @CaselIT, it feels like an open ended issue requiring a principal architectural decision on how we want to organize the core parts of the framework.
Maybe when these decisions are made and documented, it could be a relatively easy issue, but I still think we could find more fitting stuff to onboard newcomers. We actually do happen to have 12 issues labeled as such 🙂
Response has a series of utility methods for setting complex headers, like
Set-Cookie
orLink
.It would be nice to have a similar ability also in the
HttpStatus
and in theHttpError
.While ideally the interface could be duplicated/shared in a common superclass, I think that most of the benefits could be achieved by making the
_wsgi_headers
and_asgi_headers
public and setting the headers of theHttpStatus
/HttpError
to that value.falcon/falcon/response.py
Line 1049 in 113eea1
falcon/falcon/asgi/response.py
Line 390 in 113eea1
The text was updated successfully, but these errors were encountered: