-
Notifications
You must be signed in to change notification settings - Fork 15
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
Fix firefox deserialization + fix from_reader #31
base: master
Are you sure you want to change the base?
Conversation
#[serde(default = "default_fsize_maybe")] | ||
pub send: Option<f64>, | ||
#[serde(default = "default_fsize_maybe")] | ||
pub wait: Option<f64>, | ||
#[serde(default = "default_fsize_maybe")] | ||
pub receive: Option<f64>, |
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.
According to the HAR v1.3 draft spec, send
, wait
and receive
are all required fields. They even explicitly write that they are not optional, see:
https://github.com/ahmadnassri/har-spec/blob/master/versions/1.3.md#timings
#[serde(default = "default_fsize_maybe")] | ||
pub send: Option<f64>, | ||
#[serde(default = "default_fsize_maybe")] | ||
pub wait: Option<f64>, | ||
#[serde(default = "default_fsize_maybe")] | ||
pub receive: Option<f64>, |
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.
According to the HAR v1.2 spec, send
, wait
and receive
are all required fields. They even explicitly write that they are not optional, see:
Hey @grelner, thanks for opening the PR! Can the Firefox issue you're describing be solved without breaking the HAR v1.2 and v1.3 specs? Also a test reproducing the Firefox issue would be nice. |
This fixes two things: