API documentation doesn't display documentation for drafts parameters usefully
See original GitHub issueFollowing #18074, we have API documentation for the new drafts synchronization endpoints. However, while the GET endpoint renders the detailed documentation about individual fields within a draft object, the other endpoints do not, e.g.:

Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Documenting REST API resources - GitLab Docs
Writing styles, markup, formatting, and other standards for the GitLab RESTful APIs.
Read more >Set up a method request in API Gateway - AWS Documentation
Set up a method request in API Gateway · Adding an HTTP method to the method request · Configuring request parameters · Defining...
Read more >Preview API - Contentful
The Preview API will include draft entries with the same caveat that unresolved links will not appear in the includes array.
Read more >API Documentation Guide and Best Practices - Stoplight
In this API documentation guide, we'll cover the basics of how to document APIs and ... The best and most useful API references...
Read more >API Documentation - Beamer
These are the developer docs for the Beamer API. ... Some parameter is missing or doesn't follow the API specification. 401 Unauthorized.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I don’t know this code super well; @orientor or @MSurfer20 is likely better positioned to help. I think adding a missing recursive call makes sense, but I haven’t looked at the code myself.
@orientor or @MSurfer20 See this CZO chat for further questions. The above question isn’t correct. Thanks!