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
Scott, I think you're right that we should move most of the responders to a subpackage. I propose we keep SimpleResponse, StringResponse, ByteResponse, and PipeResponse in falcore proper and move all others to a new package, responder.
Thoughts?
The text was updated successfully, but these errors were encountered:
Sounds like a reasonable plan. The amount of code and docs for those responses is minimal so we can leave them where they are (or will be in the case of this repo)
I looked into adding template responders. Template is crazy complicated, though. I think users are better of using a PipeWriter and just doing the template stuff. I wonder what other responders we could include without overstepping. Maybe some built in error ones?
Some simple error ones might be nice but I think most would just be simple 1-liners around StringResponse (with empty bodies). But it seems like a lot of the other "frameworks" provide such things so I guess we could too.
Scott, I think you're right that we should move most of the responders to a subpackage. I propose we keep SimpleResponse, StringResponse, ByteResponse, and PipeResponse in falcore proper and move all others to a new package,
responder
.Thoughts?
The text was updated successfully, but these errors were encountered: