FasterXML / FasterXML/jackson-module-jsonSchema
Long data type changed to integer
- Vorherrschende Sprache
- Java
- Sterne
- 387
- Forks
- 136
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
This was mentioned in an older issue but I want to bring it up again: the JsonSchema generator does not differentiate between longs and ints. Both types end up as "integer" in the schema. It is said that when data is retrieved, it will be treated as long or int based on its size and that may be so. But when one examines the JsonSchema object, everything is "integer". You can see this from the code shown in the Readme for this package. [Here](https://github.com/ajr3-gen/long-jsonSchema/tree/main) is a very simple demonstration of it; generating a schema from an object with an `int`, a `long`, and a `Long` simply represents them all as "integer".
```
Mapped object: {
"type" : "object",
"id" : "urn:jsonschema:org:example:Demonstrator",
"properties" : {
"myId" : {
"type" : "string"
},
"myInteger" : {
"type" : "integer"
},
"myLongPrimitive" : {
"type" : "integer"
},
"myLongObject" : {
"type" : "integer"
}
}
}
```
Is there any way to preserve the original type information for the properties?
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Bewertung
Dieses Issue wurde noch nicht bewertet.