-
Notifications
You must be signed in to change notification settings - Fork 821
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
[plugin-http] update parseResponseStatus from new specs #642
Comments
What would you prefer to have instead of the switch/case? In my opinion it is plenty readable. |
Would it make sense for this logic to be shared between the web browser XHR and HTTP plugins in some way? Maybe a cc/ @obecny |
could we have an enum for that ? |
We can't have juste an enum, specs requirements need some if/else logics |
closes open-telemetry#642 Signed-off-by: Olivier Albertini <[email protected]>
closes open-telemetry#642 Signed-off-by: Olivier Albertini <[email protected]>
closes open-telemetry#642 Signed-off-by: Olivier Albertini <[email protected]>
test: fix and add tests closes open-telemetry#642 Signed-off-by: Olivier Albertini <[email protected]>
test: fix and add tests closes #642 Signed-off-by: Olivier Albertini <[email protected]>
After reading new specs, http plugin need to update
parseResponseStatus
function...I believe that
switch/case
should be removed because it will be too complex (hard to read) to handle new specs.The text was updated successfully, but these errors were encountered: