You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, AuthX follows the Relay Connection spec to support pagination, and supports unbounded requests when both first and last are omitted. Introducing a "default" limit is therefore a breaking change, as would be changing that default in the future.
I'd like to suggest requiring a value be present in either first or last. This is also a breaking change, but one that breaks things up front, as opposed to producing unexpected results some of the time. This also forces front-end and client developers to address pagination, instead of allowing it to be swept under a hope that the default is always sufficient.
The text was updated successfully, but these errors were encountered:
Currently, AuthX follows the Relay Connection spec to support pagination, and supports unbounded requests when both
first
andlast
are omitted. Introducing a "default" limit is therefore a breaking change, as would be changing that default in the future.I'd like to suggest requiring a value be present in either
first
orlast
. This is also a breaking change, but one that breaks things up front, as opposed to producing unexpected results some of the time. This also forces front-end and client developers to address pagination, instead of allowing it to be swept under a hope that the default is always sufficient.The text was updated successfully, but these errors were encountered: