Add support for bigint

[mdoi2]

I have implemented support for bigint type 😄
The schema is output as integer(int64).

If I am missing any considerations, please point them out🙇🏻‍♂️

[samchungy]

Could you update the readme otherwise lgtm

[mdoi2]

Thanks! I had overlooked that.
And I realized that each validation process should be supported like ZodNumber.
I will try to implement it, so please wait.

[mdoi2]

Oh... I was wondering why only BIgInt is not supported, maybe because metadevpro/openapi3-ts does not support bigint and you dare not support it?

[samchungy]

Thanks! I had overlooked that. And I realized that each validation process should be supported like ZodNumber. I will try to implement it, so please wait.

I'm not entirely sure what you mean by that to be honest. The contents of your PR seem fine to me

[mdoi2]

Thanks for the reply, samchungy.

maximum/minimum/multipleOf in SchemaObject is number type, so bigint cannot be set.
I have come up with the following 2 patterns to deal with this issue without changing the type.

• Exclude maximum/minimum/multipleOf from support and explain it in the README.
• Supports maximum/minimum/multipleOf only in the range of number. if the number exceeds the range, it will be excluded from the output and display warning using console.warn.

I think the latter will suffice for most of my use cases.
Please give me your opinion on this.

[samchungy]

I think if you're using bigint you're not going to really need min/max, not to mention like you said JSON Schema wouldn't be able to display it anyway

[mdoi2]

Thanks for your advice🙇🏻‍♂️ certainly agree with your thoughts.
If you can only use min/max within the range of number, you should have used number from the beginning.
And, fortunately, the range of number is wider than int32, so the possibility of needing bigint is itself low.

I have appended it to README.md.
Could you please check if everything is OK?

I did not include a note on the min/max matter, but will write one if necessary.

[samchungy]

Thanks!