You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to add support auto-generation OpenApi documentation + any UI (swagger or redoc)?
If it were possible to generate documentation automatically based on handlers signature analysis, that would be really cool. Killer feature.
I tried the crate Utoipa , but it does not have official support Ntex and is not entirely auto-generated: all the descriptions have to be done manually and as a result, the documentation can easily diverge from reality.
Thanks!
The text was updated successfully, but these errors were encountered:
Hey, i dont think it is in ntex mindset to have these feature out of the box, you should ask the creator of Utoipa if he agree to make a native ntex integration, and/or make a pull request on the utoipa repository, the code would be fairly similar to actix. As for an example I guess you already so this repository
Hey, i dont think it is in ntex mindset to have these feature out of the box, you should ask the creator of Utoipa if he agree to make a native ntex integration, and/or make a pull request on the utoipa repository, the code would be fairly similar to actix. As for an example I guess you already so this repository
Hello! I agree that the possibility of auto creating Openapi documentation is not a need for a web framework. But I think that many developers of web services use this feature when working with other technologies. Maybe exist opportunity to add elegantly example with documentation, it will be gorgeous.
Hello!
Almost any API needs good documentation.
Is it possible to add support auto-generation OpenApi documentation + any UI (swagger or redoc)?
If it were possible to generate documentation automatically based on handlers signature analysis, that would be really cool. Killer feature.
I tried the crate Utoipa , but it does not have official support Ntex and is not entirely auto-generated: all the descriptions have to be done manually and as a result, the documentation can easily diverge from reality.
Thanks!
The text was updated successfully, but these errors were encountered: