-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Closes #16224 GraphQL Pagination #18903
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.
I would not have guessed that you'd be forced to add the pagination
argument to every type class.
There are a couple of patterns to my comments/questions:
- In several type definitions, there's an extra empty line following the
pagination
parameter. Those should be removed. I started commenting them all and that just felt like overkill. - There are several type definitions I saw that did not have pagination enabled and I asked why inline. Those seemed to be mostly in the
dcim
andipam
packages.
However, there were two that I wasn't sure about, because they seem like they might be base definitions: netbox.graphql.types.ContentTypeType
and netbox.graphql.types.ObjectTypeType
. Is there a good reason not to paginate those?
Fixes: #16224