-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Request: In case of CLI method should be CLI too. #194
base: master
Are you sure you want to change the base?
Conversation
HTTP method CLI doesn't exist. |
I don't know how to better represent this (if at all). When obtaining the current Request from the DI, it should be possible to verify that the Request was created artificially in CLI mode and is not a real request. In that case, I can't rely on a number of things, such as URLs. What do you think? |
In a strict way - an HTTP request can be automatically created only via HTTP protocol so exception is more accurate. In practice - I'm not sure. |
5ace0ce
to
3affe3a
Compare
6ee31b8
to
4f4a403
Compare
a8895b6
to
9409a5f
Compare
7b7f9ff
to
78bee95
Compare
da24b94
to
540335c
Compare
e7c7e2d
to
bf945f3
Compare
9a14e6e
to
a20fb8f
Compare
55488bd
to
2042d2e
Compare
4960652
to
5e67add
Compare
689f4ae
to
33aae19
Compare
09923de
to
02ae846
Compare
In the case of obtaining a service for an Http Request in CLI mode, it does not make sense for the call method to be GET when no request exists.
I think Request should either throw an exception that cannot be used in a CLI context, or it should return a special CLI method.
Current behavior looks illogical:
Thanks.