Tracking Issue for 0.16.0 Release

[baxterjo]

This is the tracking issue for the release of 0.16.0, which will include some breaking changes:

• schemars bumped to version 1
  • As a user it is important to bump your own schemars version in Cargo.toml as both 0.9.0 and 1 can be added as dependencies but the trait bounds for aide methods will no longer be satisfied and will have cryptic errors.
• Uses StatusCode instead of u16 for inferred responses
• Upgrade to axum-extra 0.12

[baxterjo]

@jplatte feel free to close this if I'm overstepping, or completely rewrite the description. But I need a way to track the schemars upgrade.

[jplatte]

Thanks! This is helpful :)

[jwulfheide-gb]

As a user it is important to bump your own schemars version in Cargo.toml as both 0.9.0 and 1 can be added as dependencies but the trait bounds for aide methods will no longer be satisfied and will have cryptic errors.

btw. in this regard. does it seem reasonable to you to have aide re-export the trait definitions of schemars? that way users would not need to explicitly depend on schemars. trait definition and trait implementation would always match.

[nCrazed]

As a user it is important to bump your own schemars version in Cargo.toml as both 0.9.0 and 1 can be added as dependencies but the trait bounds for aide methods will no longer be satisfied and will have cryptic errors.

btw. in this regard. does it seem reasonable to you to have aide re-export the trait definitions of schemars? that way users would not need to explicitly depend on schemars. trait definition and trait implementation would always match.

Came looking for this issue/comment after being surprised that this isn't already the case

[jplatte]

I'm surprised I didn't post this here before, but a pre-release is available: https://crates.io/crates/aide/0.16.0-alpha.2

As it stands I don't have much time for open source in general, but this is one of my higher priorities for when I get some focus time again.

[abbudao]

@jplatte is there anything specific I can help with for the 0.16 release? I'd be glad to take on any of the remaining blockers.

[jplatte]

You could probably help with #230, which has been abandoned by its author and needs a test. Probably best to start a new branch, cherry-pick the second commit since the first was already merged, then add another with a test.

[abbudao]

@jplatte opened #301 in attempt to solve the bug reported on #230. If there is anything else you want done for 0.16.0, feel free to ping me.