-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
js/k6/http: Fix lint errors #3566
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #3566 +/- ##
==========================================
+ Coverage 72.82% 72.97% +0.14%
==========================================
Files 278 280 +2
Lines 20947 20951 +4
==========================================
+ Hits 15254 15288 +34
+ Misses 4715 4692 -23
+ Partials 978 971 -7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
b, ok := resp.Body.([]byte) | ||
if !ok { | ||
panic("got an unexpected type for the response body, only []byte is accepted") | ||
} | ||
resp.Body = c.moduleInstance.vu.Runtime().NewArrayBuffer(b) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There really is no way for this to happen apart from programming error on our side.
I am not against hte change - but arguably:
- just a nolint would've been simpler
- this panic should mention this is a programming error.
Updates #769