This repository was archived by the owner on Dec 25, 2025. It is now read-only.

Description
Describe the bug
Encountered that fabrix fails to parse GraphQL response in cursor pagination style
TypeError: Cannot read properties of undefined (reading 'map')
at tt (fabrix.mjs:1:7626)
at G (fabrix.mjs:1:8113)
at he (fabrix.mjs:1:19580)
at react-stack-bottom-frame (react-dom-client.development.js:23609:20)
at renderWithHooks (react-dom-client.development.js:4645:22)
at updateFunctionComponent (react-dom-client.development.js:8031:19)
at beginWork (react-dom-client.development.js:9688:18)
at runWithFiberInDEV (react-dom-client.development.js:543:16)
at performUnitOfWork (react-dom-client.development.js:15063:22)
at workLoopSync (react-dom-client.development.js:14887:41)
at renderRootSync (react-dom-client.development.js:14867:11)
at performWorkOnRoot (react-dom-client.development.js:14393:44)
at performWorkOnRootViaSchedulerTask (react-dom-client.development.js:15954:7)
at MessagePort.performWorkUntilDeadline (scheduler.development.js:44:48)
The thing that I know currently is that the case that data goes {} during the data fetch is not fully coverred.
|
return (value.edges as { node: Record<string, unknown> }[]).map( |
|
({ node }) => node, |
|
); |
Steps to reproduce
Not spotted
Expected behavior
No error should happen.
Environment
N/A
Additional context
N/A