Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add pagination to bugsnag and generic api controller #72
Add pagination to bugsnag and generic api controller #72
Changes from 2 commits
68168ba
bdfc6a7
f6c361b
767ee7e
00dc9cd
efab948
5c1bfcf
7795bd1
02ea4b8
7288d2b
a2146c3
755a900
99d364b
af9ad88
affc874
530f20e
7e59e7a
0c800e4
44c6c77
7c1e133
d6e236d
ace5772
692c66a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I suppose this is a little better than the AdminUser[] type since the definition for that was just an empty object. It might be out of scope for this PR, but it would be nice to have the swagger docs include refs to the proper object in an array.
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.
@evansiroky Note that
AdminUser
is a subclass ofAbstractUser
, but spark-swagger ignores inherited fields at the time this was implemented. We insert inherited fields into theAdminUser
swagger type using thePublicApiDocGenerator
class.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.
This is going to be incorrect since at the very least the items will be an object. It might be necessary to have separate ResponseList types that include the correct reference to the subclass that they return.
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.
@binh-dam-ibigroup, do you have any thoughts on how to ammend this swagger def?
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.
The most thorough way to handle this would be to change the document generator class to create a
ResponseList_Subtype
object definition for each of theResponseList
responses we are publishing. We can also try creating a separate descendant ofResponseBody
per @evansiroky's suggestion above and see how spark-swagger handles that.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.
To follow up on my comment above, you could modify class
PublicApiDocsGenerator
to do the following:ResponseList
return entries in the autogenerated swagger.ResponseList<type>
ResponseList
with the custom type generated above.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.
Further discussion should be had in #85