-
Notifications
You must be signed in to change notification settings - Fork 324
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
Render Named
names as "internal route ID" in swagger UI.
#3319
Conversation
(makes grepping for source code easier.)
... like `("put", Wire.API.Team.Feature.LegalholdConfig))`. oumphf.
& allOperations . summary %~ (<> Just dscr) | ||
& allOperations . description %~ (Just (dscr <> "\n\n") <>) |
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.
not sure we want both, but i can't decide which one to prefer?
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.
Let's keep the one in the description, not the summary
i also thought maybe we can make it a rule that the internal IDs are strings that can be fed to grep verbatim. and maybe document this in docs.wire.com somewhere, and link to those docs from the "internal route ID" label. |
This should make jumping from swagger docs into the source code by grepping for the ID much easier.
Checklist
changelog.d