fix(jq): preserve fractional scalar precision - #305
Closed
efegokdemir wants to merge 1 commit into
Closed
efegokdemir wants to merge 1 commit into
efegokdemir wants to merge 1 commit into
Conversation
Signed-off-by: Efe Gökdemir <efe@rexcode.co.uk>
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.
Summary
jq.Evaluatecurrently formats non-integer scalar values with exactly two fractional digits, which turns values such as0.001into0.00. This preserves the value's meaningful decimal representation instead.Changes
strconv.FormatFloatprecision-1.0.001.Testing
go test ./pkg/jqgo test ./...git diff --checkAll passed.
Notes
The issue is not duplicated by an existing open PR: the only open PR mentioning
256is unrelated to this change. The approach follows the maintainer's issue discussion that the truncation is unexpected and should be fixed without changing the public API.AI assistance was used to investigate the issue, implement the focused change, and run the tests. I reviewed the complete diff and am responsible for the submitted change.
Fixes #256