Should an async createMemo re-run when it updates its own reactive dependency?

[corluk]

Async createMemo with pagination keeps re-running when nextCursor is updated from the fetched result

Description

I'm testing the async createMemo behavior in Solid 2.0.

I have a paginated API where each response contains a nextCursor. The cursor is stored in a signal and is also used as a dependency of an async createMemo.

After each request, I update the cursor with the nextCursor returned by the API.

Something similar to:

const [cursor, setCursor] = createSignal<string | undefined>(undefined);

const albums = createMemo(async () => {
  const json = await fetchAlbums(cursor());

  setCursor(json.nextCursor ?? undefined);

  return json.data;
});

Because cursor() is read inside the memo, changing it after the request causes the memo to run again.

As a result, the behavior becomes:

cursor = undefined
↓
fetch page 1
↓
setCursor(page2Cursor)
↓
memo reruns
↓
fetch page 2
↓
setCursor(page3Cursor)
↓
memo reruns
↓
...
↓
nextCursor = null

So simply reading the first result ends up fetching all pages until the API returns nextCursor: null.

Question

Is this the expected behavior for async createMemo in Solid 2.0?

I understand that cursor() becomes a reactive dependency of the memo, so from the fine-grained reactivity perspective the reruns make sense.

However, since Solid 2.0 encourages using async createMemo directly for data fetching, I'm wondering whether updating a pagination signal as a consequence of the same request is expected to recursively invalidate the memo in this way.

Should pagination state instead always be updated outside of the memo, for example in response to an explicit "Next page" action?

Or is there a recommended Solid 2.0 pattern for this type of cursor-based pagination?

Expected behavior / clarification requested

I'm mainly looking for clarification on whether:

1. This recursive request behavior is intentional and expected.
2. Updating reactive state from an async memo that is also one of the memo's dependencies should be avoided.
3. There is a recommended pattern in Solid 2.0 for cursor-based pagination using async createMemo.

Environment

solid-js: 2.0.0-rc.x