i32 impossible to set

[MichalNemec]

Truly awesome generator, kudos to you!

I have issue with i32

{
            "name": "limit",
            "in": "query",
            "required": false,
            "schema": {
              "type": "integer",
              "format": "int32",
              "default": 20,
              "maximum": 100,
              "minimum": 1
            }
          },

Whatever i do, i.e:

[type_mappings]
"Int32" = "i32"
"Integer" = "i32"

[generator.types.strategies]
"int32" = "i32"
"integer" = "i32"

i always get i64. https://github.com/gpu-cli/openapi-to-rust/blob/main/src/analysis.rs#L4564 does not take it into account.
Can i have some direction on how to achieve i32?

[lightsofapollo]

@MichalNemec thanks for the report and including the schema! I will take a look and give some guidance or release a fix.

[lightsofapollo]

Thanks for the kind words and the clear repro! 🙏

Root cause confirmed. Query and path parameters were ignoring the schema format. analyze_parameter hardcoded integer => i64 (and number => f64) and never went through the TypeMapper that the schema-property path uses. So an int32 field inside a request/response body correctly became i32, but the same format: int32 on a query/path parameter always became i64. Because the mapper was skipped entirely, your [type_mappings] / [generator.types.strategies] entries never got a chance to apply either — which is exactly why "whatever I do, I always get i64."

Fix is up: #24. Parameters now resolve their integer/number type through the same mapper as properties:

• int32 -> i32, int64 -> i64
• float -> f32, double -> f64
• formatless integer stays i64
• [type_mappings] / strategy config now applies to parameters too

With this, your limit parameter generates as i32 (and once the built-in int32 -> i32 mapping kicks in, you won't even need the extra config). CI is green; it'll land shortly after review.

[lightsofapollo]

Released in v0.5.2 — now on crates.io. cargo update -p openapi-to-rust (or bump to 0.5.2) and regenerate: your limit parameter will come out as i32. Thanks again for the report! 🚀