-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Optional Support for Rocket-Okapi Integration in IntrospectedUser #558
Comments
i would try to implement it, atm i am struggling to develop the project but i could test the new features of course! |
Hello @NewtTheWolf, thanks for implementing this. I am also interested in this feature. @buehler Can I somehow support this to appear in the next zitadel version? |
Uh, someone is intrested, atm i am using a Tuplestruct to Achive it But i will implement it correctly later that day in my Draft Pull so it could be Merged |
@pustekuchen91 do you have an idea by any chance? |
Hey @pustekuchen91 @NewtTheWolf Thanks for the proposals. This sounds reasonable :-) I currently have no time to implement such a thing, but feel free to create a PR which I'll happily review ;-) |
hey @buehler i already implemented it in the linked PR could you maybe already do a little review? |
Hello @buehler and @NewtTheWolf , I am also interested in this feature. Is there some way to support this effort? |
Implemented with #559 |
Feature Request: Optional Support for Rocket-Okapi Integration in
IntrospectedUser
Description
I propose integrating the
rocket-okapi
library as an optional feature in thezitadel-rust
project, specifically by implementing theOpenApiResponderInner
and/orOpenApiResponder
traits in theIntrospectedUser
type. This enhancement would enable OpenAPI specification support for Rocket-based applications, facilitating automated API documentation generation.Motivation
Adding
rocket-okapi
support as an optional feature would improve the developer experience by providing automated API documentation generation capabilities, without imposing additional overhead on those who do not require this functionality. It is particularly useful for teams that need to maintain clear and accurate API documentation in fast-paced development environments.Suggestion
The feature should be implemented as non-default, allowing developers to opt in as needed. Implementing the required traits in
IntrospectedUser
would make it straightforward to generate API documentation for services that utilize this type.Possible Implementation Steps:
IntrospectedUser
type to implement theOpenApiResponderInner
andOpenApiResponder
traits.zitadel-rust
project to keep it optional.Conclusion
Integrating
rocket-okapi
as an optional feature withinIntrospectedUser
could greatly enhance the capability of developers to maintain robust API documentation with minimal overhead. This feature would be particularly advantageous for projects requiring detailed and accurate API specs without disrupting the current project setup. I am eager to hear your thoughts and suggestions regarding this proposal.Thank you for considering this feature request.
rocket-okapi GitHub Link
The text was updated successfully, but these errors were encountered: