Properly format numbers parsed from jsonPath outputs#1755
Merged
carolynvs merged 1 commit intogetporter:mainfrom Sep 15, 2021
Merged
Properly format numbers parsed from jsonPath outputs#1755carolynvs merged 1 commit intogetporter:mainfrom
carolynvs merged 1 commit intogetporter:mainfrom
Conversation
When we parse outputs for jsonPath expressions, numbers are not being formatted as expected. For example, a number like "123123123" is being output as "1.23123123e+08". This is due to how we are parsing the jsonPath. The output is marshaled into a generic map, where json numbers are represented as float64. We use fmt.Sprintf to format the matching output value, and Go by default formats float with %f/%g, neither of which is the desired format. I've updated our json parsing to use the Number type so that the format of the captured value matches what was used in the original output. Signed-off-by: Carolyn Van Slyck <me@carolynvanslyck.com>
vdice
approved these changes
Sep 14, 2021
Member
Author
|
I'm going to hold off on anymore merges until our free oss status is fixed in Azure DevOps. That's why all the builds immediately fail. 💰 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this change
When we parse outputs for jsonPath expressions, numbers are not being formatted as expected. For example, a number like "123123123" is being output as "1.23123123e+08".
This is due to how we are parsing the jsonPath. The output is marshaled into a generic map, where json numbers are represented as float64. We use fmt.Sprintf to format the matching output value, and Go by default formats float with %f/%g, neither of which is the desired format.
I've updated our json parsing to use the Number type so that the format of the captured value matches what was used in the original output.
What issue does it fix
Fixes #1754
Notes for the reviewer
They who provide test data to reproduce, get fast bug fixes. ❤️
Checklist