Edge Cursors nullable
mjquinlan2000 opened this issue · 1 comments
Is there a reason that Edge cursors are nullable now? We're getting compatibility check errors in our CI pipeline because the edge cursor definition has changed from String!
to String
Edit:
I'm using {:absinthe_relay, "1.5.0-beta.0"}
Nevermind. I was just checking the Relay docs and this is what the specification is
Cursor
An “Edge Type” must contain a field called cursor. This field must return a type that serializes as a String; this may be a String, a Non‐Null wrapper around a String, a custom scalar that serializes as a String, or a Non‐Null wrapper around a custom scalar that serializes as a String.Whatever type this field returns will be referred to as the cursor type in the rest of this spec.
The result of this field is considered opaque by Relay, but will be passed back to the server as described in the “Arguments” section below.
Cursors can be nullable.