fetchMore is easy to use wrong

[humancatfood]

I have just submitted a PR at work that uses infinite-query.

One of the first comments I got back was that, instead of doing

onClick={() => fetchMore()}

I could just do

onClick={fetchMore}

I explained how that would override the cursor and pointed them at the documentation, but it did occur how easy it would be for a maintainer to accidentally break this by drive-by-optimisation. I don't want to clump up my code with comments warning people to not touch my callbacks.

Would it make sense to put the warning from the documentation into the inner fetchPage function in Query.startInfiniteFetch?

if (cursor instanceof Event) {
  Console.warn(`fetchMore received an Event as parameter!

Note: It's very important you do not call fetchMore with arguments unless you want them to override the fetchMoreInfo data returned from the getFetchMore function. eg. Do not do this: <button onClick={fetchMore} /> as this would send the onClick event to the fetchMore function

${new Error().stack.slice(6)}

  `)
}