Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add useJSONNumber to Plan and amend UnmarshalJSON behavior #113

Merged
merged 3 commits into from
Dec 18, 2023
Merged

Add useJSONNumber to Plan and amend UnmarshalJSON behavior #113

merged 3 commits into from
Dec 18, 2023

Conversation

bendbennett
Copy link
Contributor

Closes: #111

@bendbennett bendbennett added the enhancement New feature or request label Dec 7, 2023
@bendbennett bendbennett requested review from a team as code owners December 7, 2023 15:04
This was referenced Dec 8, 2023
Closed
Merged
@bendbennett bendbennett mentioned this pull request Dec 18, 2023
Merged
@bendbennett bendbennett merged commit 41fa8df into main Dec 18, 2023
8 checks passed
@bendbennett bendbennett deleted the bendbennett/issues-111 branch December 18, 2023 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kmoe kmoe kmoe approved these changes

Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Consider allowing configuration of tfjson.Plan to use JSON number
2 participants
@bendbennett @kmoe