openapi integers range.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1.2k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 21
Description
Hi, @FallenDeity , could you help me here if you have some spare time? I wanted to regenerate the openapi schema on my PC but I get a different result than the current version on master, when building many properties get this modification:
growth_time:
type: integer
- maximum: 2147483647
- minimum: -2147483648
+ maximum: 9223372036854775807
+ minimum: -9223372036854775808
+ format: int64
Can we add a rule for these ranges?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named; start by locating the OpenAPI schema-generation entry point and the rule that maps integer ranges, then compare its output with master. Done means regeneration consistently produces the intended integer ranges instead of the shown 64-bit values and int64 format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100