Is it possible to use int32 for integer types in the OpenAPI documentation?

[crgeary]

It looks like integer types are converted into int64 values, this results in a problem when trying to generate Zod schemas from the spec using @hey-api as it converts int64 to bigint types.

Code within @hey-api:
https://github.com/hey-api/openapi-ts/blob/main/packages/openapi-ts/src/plugins/zod/plugin.ts#L287-L313

Given that int64 (9223372036854775807) values will not fit within int32 (2147483647) systems, I would expect to be able to set the correct format that matches what the current system supports in order to provide the correct hints to tools.

It looks like I can't get the desired result with numericRange unless I am mistaken 🤔

I'm not sure what I would expect the solution to be, perhaps either:

• an option for Documentation to specify the integer format to use like int32 or null to omit it from numbers
• use numericRange and pick int64 or int32 dependant on the supplied range

Thanks as always for your work on this project.

[RobinTail]

Yeah, the issue is that JavaScript's safe integers are greater than int32 but lesser than int64.
I tried to express it with format: int64 but also setting maximum and minimum according to the safe or the specified range.

Not sure yet how to correct it for this case.
Perhaps I could use the second option from your suggestion, @crgeary

I will check it out a bit later (trying to adopt zod 4) — there will be no such issue.

[RobinTail]

Check out the suggested approach, @crgeary : #2641

Depending on numericRange it can be either int32 | int64 | undefined.

Would that suit your needs?

[crgeary]

@RobinTail yeah this is great and looks like it would solve the problem, thank you! Thank you for such a speedy reply on this as well.

[RobinTail]

@crgeary 🚀 v23.5.0