-
Notifications
You must be signed in to change notification settings - Fork 108
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
API documentation improvements #3365
Conversation
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.
First installment....
1742d62
to
cbe04c7
Compare
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.
That's great stuff, it just needs a round of polishing. And, there is a question or two which is more to do with the design/implementation than the documentation, but the two should match....
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.
Um, Dave? Your documentation improvements failed the unit tests.... 😬 |
It would appear that |
@npalaska...it appears you touched the code last.... 👁️ |
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.
You've resolved all but one of my previous comments, but...with new updates come new comments....
There's a misspelling which should be fixed, and I'd like to see more rework around the removal of "user" as a resource; other than those, I've got a couple of questions, and the rest are lesser suggestions or nits.
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.
You've resolved all but #3365 (comment) of my previous comments
I truly loathe GitHub for reviews. I made an attempt to trace all the open conversations, but GitHub makes that at least 1000 times as difficult as it should be, and it's really easy to miss things. 😦
PBENCH-829 Fill out and (to some extent update) API documentation. I debated removing the "user" APIs now even though they still technically exist, and perhaps I should ...
As long as we're griping about GitHub's review support, I'll note that some of the replies that you posted an hour ago were composed yesterday afternoon...although that might not be entirely GitHub's fault. 😉 |
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.
Looks good to me...we just need a Jira ticket so we don't forget about reconciling the filtering options for /datasets/daterange
with the analogous support for /datasets
.
(Although, now that I look at it, /datasets/daterange
doesn't look properly resource-centric...shouldn't daterange
be a query parameter?...making that change might result in the convergence of the filtering options....)
PBENCH-1125, by the way, which I've now coded and tested; and will post as a PR once this PR goes in so I can first modify the documentation to match. 😁 And BTW I loved the suggestion of merging this with |
PBENCH-829
Fill out and update API documentation.