-
Notifications
You must be signed in to change notification settings - Fork 20
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
[API] Enhance the Request
class
#117
Comments
Any reason we don't just want to compose rack behavior similar to how rails is achieving this behavior by including https://api.rubyonrails.org/v8.0.1/classes/ActionDispatch/Request.html Reviewed both those Rack modules and it looks like that's where the methods are implemented. I was able to implement
And it looks like that works |
Huh, I guess I didn't realise it existed. Let's use these modules - it makes perfect sense. |
Ok. Just need to make sure that these are being used correctly / if im missing anything right now, still digesting the code from the rage, rails, and rack |
Do we just want to hook into rails for some of the messages that we're missing for e.g. instead of a |
We definitely don’t want to introduce the Action Dispatch dependency. And the implementation indeed seems straightforward. |
Description
Compared to Rails’
Request
class, Rage’s Request currently has very few methods.We'd like to update the class to include the following methods:
host
domain
method
get?
/post?
/patch?
/put?
/delete?
/head?
port
protocol
query_string
remote_ip
env
Tips
The text was updated successfully, but these errors were encountered: