We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
useProxy
Currently there is a possibility to configure web proxy with "true" value. This makes the code unclear: see also the discussion for pull request at:
"true"
For resolution I like the second approach more:
there will be only named type of a proxy (remove true as a possible value) after deprecating it first for e.g. 2 minor versions
(Alternative solution is to have the configuration value "default" be interpreted as "rest" proxy.)
"default"
"rest"
Currently all suites using web proxy have it configured to "rest" as otherwise it doesn't work.
The text was updated successfully, but these errors were encountered:
As currently true does not work, i think we can get rid of it with no deprecated period.
true
Sorry, something went wrong.
Fixes #56 - clean configuration legacy for useProxy configuration
0c10f3d
No branches or pull requests
Currently there is a possibility to configure web proxy with
"true"
value.This makes the code unclear: see also the discussion for pull request at:
For resolution I like the second approach more:
(Alternative solution is to have the configuration value
"default"
be interpreted as"rest"
proxy.)Currently all suites using web proxy have it configured to
"rest"
as otherwise it doesn't work.The text was updated successfully, but these errors were encountered: