I’ve noticed than unlike what’s stated in the docs, model.ContentMatch.edge can return nullable fields.
Indeed, it we look at the sources, it should throw a
i >= this.next.length instead of
i > this.next.length like it is right now, if we consider n starts at 0 (maybe this should be clarified too).
I can create an Issue and/or a PR if needed.
Thanks for all the huge work you’ve done