Do not break when after is greater than list_length

[bellini666]

I added a test that, without the change do graphene_django/fields.py breaks with the traceback described in the issue bellow.

Fix #998

[jkimbo]

Thanks for the raising this issue @bellini666 . I'm wondering if it would be better if an error was raised (one that it is more helpful) rather than silently accepting an after value which is greater than the list length. What's the situation where your client is passing an after value that is greater than the list length?

[bellini666]

Hi @jkimbo .

Yeah, I thought of that too, that probably the client should be more careful when passing an after keyword. But on the other hand, if we think of this in terms of python slicing or even sql limit/offset, if you pass something an offset greater than the list/result's length will be an empty list/set and will be silently regarding the "issue".

Another way to look at this is to do what the relay specifications (or the original node implementation) does. If it says to raise an error then we should definitely raise an error =P

[wkoot]

I don't think it would be weird to return an empty set as it is the default behaviour for filtering in general.
Say I filter field_Icontains: "non_existant" I would also recieve an empty result, without errors :)
Perhaps it would be useful to return such warnings in a meta field though. Is there anything about it in the spec?

[jkimbo]

Sorry for the delay @bellini666 . I've been thinking about this a lot and I agree with yours and @wkoot argument so I'm going to merge this.

Perhaps it would be useful to return such warnings in a meta field though. Is there anything about it in the spec?
As far as I know there isn't anything in the spec about this.

[jkimbo]

Released this in v2.11.1