Move utoipa behind feature flag

[KrausMatthias]

Hi :)

would it be possible to move utoipa behind a feature flag using https://doc.rust-lang.org/reference/conditional-compilation.html#the-cfg_attr-attribute? Unfortunately in my project the API Spec is generated via JsonSchema + Aide

Would be ready to add another (hopefully faster) PR :)

[b4l]

Feature gating utoipa certainly makes sense. Maybe JsonSchema could be added in the same way? I assume it is required for the types to implement it?

What made you go for aide? I looked into it and then went with utoipa. I like to have the doc on the handler (macro). However, I can see that aide could offer more composability, so switching to it entirely is also an option, in case the documentation ends up the same.

[KrausMatthias]

To be honest I had a hard time deciding between utoipa and aide, I went for aide because I thought it might be easier to build a dynamic api spec with it that includes collections / CRUD methods on collections based on an authenticated user (as that is what e.g. QGIS is using to decide if a collection is editable or not). Didn't get around to try that so far, so I might be wrong. I'm mimicking that behavior in https://codeberg.org/OpenGeoMesh/ogm-demo-stack/src/branch/main/frontend/index.html#L63

actually you are already using schemars in processes and services

[b4l]

An alternative might be predefined scopes; however, aide is probably the way to go to make it composable and allow reusing the handler functions.