You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to #705 (comment), the json path library we use to parse arbitrary payloads in the web metric, returns result values as strings. It should return the result in the original format, so that functions like asFloat are not necessary if the data is already in the desired format.
Diagnostics
v0.9
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered:
We're not using jsonParser to its fullest potential because we call the Execute convenience method which loses the information about the type. If we switch to jsonParser.FindResults(), we will get reflect.Values which indicate the original type.
err=p.jsonParser.Execute(buf, data) // this loses informationiferr!=nil {
return"", v1alpha1.AnalysisPhaseError, fmt.Errorf("Could not find JSONPath in body: %s", err)
}
out:=buf.String()
Summary
According to #705 (comment), the json path library we use to parse arbitrary payloads in the web metric, returns result values as strings. It should return the result in the original format, so that functions like
asFloat
are not necessary if the data is already in the desired format.Diagnostics
v0.9
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: