OpenAPITools / OpenAPITools/openapi-generator

[BUG] [Go] Json Unmarshal int bigger then int64

Open
#10,620 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Client: Go Issue: Bug
Dominant language
Java
Stars
26.8k
Forks
7.7k
PR merge metrics
PR metrics pending

Description

Bug Report Checklist
  • Have you provided a full/minimal spec to reproduce the issue?
  • Have you validated the input using an OpenAPI validator (example)?
  • Have you tested with the latest master to confirm the issue still exists?
  • Have you searched for related issues/PRs?
  • What's the actual output vs expected output?
  • [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description

in the go generator, trying to unMarshal big int values, get overflow on int64


package main

import (
	"encoding/json"
	"fmt"

	"github.com/danijeel/bigintexample/openapi"
)

func main() {
	jsonSrc := []byte(`{
		"id": 162259276829213363391578010288126,
		"name": "test"
	}`)
	var myJson openapi.Category
	json.Unmarshal(jsonSrc, &myJson)
	fmt.Printf("%d\n", myJson.Id)
	// output: 824634459072
	// expects: 162259276829213363391578010288126
}

Full example can be seen here: https://github.com/danijeel/bigintexample/blob/main/main.go

openapi-generator version

5.2.1

OpenAPI declaration file content or url

The openapi example specification is based on the petstore example
https://github.com/danijeel/bigintexample/blob/eb590428c496e152ec32ff30a6464b2849b74a7b/openapi.yml

Generation Details
Steps to reproduce
Related issues/PRs
Suggest a fix

In the branch patch-big-int
I replaced the int64 attribute with custom type BigInt in the category model

https://github.com/danijeel/bigintexample/commit/97dde59dd7b6ec4aa136431de31268dda248bb74

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the overflow with the linked openapi.yml and the Go example in main.go, then inspect the generated openapi.Category model and its Id field. Compare the generated int64 field with the custom BigInt change in the linked patch-big-int branch. Done should mean the generated Go model preserves the large JSON integer instead of producing the shown overflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.