-
Notifications
You must be signed in to change notification settings - Fork 1
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
Generate OpenAPI spec using Utoipa #122
base: main
Are you sure you want to change the base?
Conversation
The question right now would be: Is this going in the right direction? |
899661c
to
e84f01f
Compare
I think this feature works nicely now and does not hurt ergonomics too much, but I could use some opinions on particularly the ergonomics of the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My general feeling is on the one hand side, I can see how this is useful in some cases while on the other hand, it introduces a ton of new concepts and accidental complexity… I'm a bit torn – might well be good to have this but likely opt-in. At the same time, I'm not sure this should be the priority for now when we have a number of other things to figure out first:
- relations between entities
- some kind of background job functionality
- deployment story (might only be documentation but I guess regarding e.g. how to run migrations on production during deployment, we have some blind spots)
@marcoow thanks for the insight. I agree we may need to do some more thinking/experimenting before adding a feature like this. I'll add issues for the things you listed |
@hdoordt I wouldn't necessarily suggest to close this – I think it can be useful and we could do it at some point, I just think we'd need to think about how we add this exactly |
I don't know what happened there, but closing the PR was not intentional. Reopening it |
Very much an experiment as of right now, but this PR aims to: