Models often use `Option<Box<...>>`

[jannic]

Types representing requests or response data often use types like Option<Box<String>>. For example:
https://github.com/fastly/fastly-rust/blob/release/v1.1.0/src/models/version_create_response.rs#L16

What's the reason for using a Box here? It seems unnecessary and leads to clumsy code handling those data structures.

[jannic]

Another observation: This seems to happen for Strings used as an id. I didn't find the openApi spec this code is generated from, so I couldn't check myself: Are those fields defined in a somehow special way? It seems like the isModel flag is true for those. The Rust generator uses Box if isModel is true, to avoid problems with recursive types. But that's of course not necessary for fields of type String.

[Integralist]

👋🏻 Thanks for opening this issue @jannic

Just to let you know we have now opened an internal ticket to track this issue.