✅ Make default number range for z.number() configurable

[APTy]

Description

This feels like it'd be a common issue, but there's very little information about it online, and the error message is not very clear.

It occurs when using z.number() in your types and then trying to generate HTML docs based on that.

  Exception: Character I is neither a decimal digit number, decimal point, nor "e" notation exponential mark.
	at org.openapitools.codegen.DefaultGenerator.processOperation(DefaultGenerator.java:1610)
	at org.openapitools.codegen.DefaultGenerator.processPaths(DefaultGenerator.java:1475)
	at org.openapitools.codegen.DefaultGenerator.generateApis(DefaultGenerator.java:677)
	at org.openapitools.codegen.DefaultGenerator.generate(DefaultGenerator.java:1307)
	at org.openapitools.codegen.cmd.Generate.execute(Generate.java:535)
	at org.openapitools.codegen.cmd.OpenApiGeneratorCommand.run(OpenApiGeneratorCommand.java:32)
	at org.openapitools.codegen.OpenAPIGenerator.main(OpenAPIGenerator.java:66)
Caused by: java.lang.NumberFormatException: Character I is neither a decimal digit number, decimal point, nor "e" notation exponential mark.
	at java.base/java.math.BigDecimal.<init>(BigDecimal.java:608)
	at java.base/java.math.BigDecimal.<init>(BigDecimal.java:497)
	at java.base/java.math.BigDecimal.<init>(BigDecimal.java:903)
	at java.base/java.math.BigDecimal.valueOf(BigDecimal.java:1371)
	at org.openapitools.codegen.examples.ExampleGenerator.resolvePropertyToExample(ExampleGenerator.java:271)
	at org.openapitools.codegen.examples.ExampleGenerator.traverseSchemaProperties(ExampleGenerator.java:392)
	at org.openapitools.codegen.examples.ExampleGenerator.resolveModelToExample(ExampleGenerator.java:361)
	at org.openapitools.codegen.examples.ExampleGenerator.resolvePropertyToExample(ExampleGenerator.java:322)
	at org.openapitools.codegen.examples.ExampleGenerator.traverseSchemaProperties(ExampleGenerator.java:392)
	at org.openapitools.codegen.examples.ExampleGenerator.resolveModelToExample(ExampleGenerator.java:361)
	at org.openapitools.codegen.examples.ExampleGenerator.generate(ExampleGenerator.java:161)
	at org.openapitools.codegen.examples.ExampleGenerator.generateFromResponseSchema(ExampleGenerator.java:97)
	at org.openapitools.codegen.examples.ExampleGenerator.generateFromResponseSchema(ExampleGenerator.java:63)
	at org.openapitools.codegen.DefaultCodegen.fromOperation(DefaultCodegen.java:4702)
	at org.openapitools.codegen.DefaultGenerator.processOperation(DefaultGenerator.java:1578)
	... 6 more

It seems related to OpenAPITools/openapi-generator#12111. If that issue author's theory is correct, then maybe a solution would be for zod-express-api to use a default min/max of min(-1 * Number.MAX_VALUE / 10).max(Number.MAX_VALUE / 10).

Expected

I expected to be able to use a z.number() type and then generate HTML docs based on that.

Reproduction

1. Create an API route that uses z.number() in one of the types
2. Use new Documentation({ ... }).getSpecAsYaml() and write to api.yaml
3. Generate HTML docs with openapi-generator-cli generate -g html -i api.yaml

Workarounds

Currently, using z.number().int() is a workaround if you don't need decimal precision. Or you can also set reasonable min().max() manually based on your use case.

EDIT: Probably using these workarounds is the correct thing to do until the problem is fixed in openapi-generator project.. it does seem like express-zod-api's behavior working as intended, and it's the other library that is broken.

Context

• Node.js version: >=18.0.0
• express-zod-api version: ^19.2.2

Appreciate your help!

[RobinTail]

@APTy , this is not a bug of express-zod-api, it's the bug of the third party software you're using.

The theory of the original issue's author is most likely correct, but it does not mean that express-zod-api should divide MAX_VALUE by 10. No, it means that the difference between min and max should not be assigned to a variable having the type that can not fit such number.

Please refer to the maintainer of openapi-generator for elaborating on its fix.

Meanwhile, until the bug in that generator is not fixed, you'd have to set min and max manually, as a workaround for the particular case.

[LufyCZ]

@APTy , this is not a bug of express-zod-api, it's the bug of the third party software you're using.

The theory of the original issue's author is most likely correct, but it does not mean that express-zod-api should divide MAX_VALUE by 10. No, it means that the difference between min and max should not be assigned to a variable having the type that can not fit such number.

Please refer to the maintainer of openapi-generator for elaborating on its fix.

Meanwhile, until the bug in that generator is not fixed, you'd have to set min and max manually, as a workaround for the particular case.

I've come across this issue multiple times as well, and IMO, the solution here would be not including the max and min attributes at all unless they are specified in the zod schema. wdyt?

[RobinTail]

Well... I'm still not sure about this, @LufyCZ

• The aim of the Documentation generator is to depict the API as good as possible;
• Since the API is operated by a JavaScript engine, the range of acceptable numbers is limited by the environment and I find it beneficial that it can be described out of the box;
• The issue of a particular tool dealing with that depiction should not justify reducing the functionality;

Taking all that into account, I presume, that it could be configurable.

[RobinTail]

🚀 in v22.11.0 you can disable the default min/max range by setting numericRange: null option on the Documentation, @LufyCZ && @APTy

[LufyCZ]

Thanks!