You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Want to say, this library is great.. maybe i'll find time to dive in and try to work this out myself, but if not:
Inlining function components wrapped in memo() returns this error:
TypeError: renderMethod is not a function
at node_modules/isolate-components/lib/isolatedRenderer/index.js:27:28
at render (node_modules/isolate-hooks/lib/index.js:38:40)
at Object.render (node_modules/isolate-components/lib/isolatedRenderer/index.js:33:9)
at forEach (node_modules/isolate-components/lib/nodeTree/inline.js:16:43)
at Array.forEach (<anonymous>)
at Object.doInline (node_modules/isolate-components/lib/nodeTree/inline.js:14:23)
at forEach (node_modules/isolate-components/lib/nodeTree/inline.js:20:21)
at Array.forEach (<anonymous>)
at Object.doInline (node_modules/isolate-components/lib/nodeTree/inline.js:14:23)
at node_modules/isolate-components/lib/nodeTree/inline.js:20:21
When not inlining, they appear as <undefined ...> in toString() output.
It'd be great to support them if it's a simple thing!
isolate-components v1.1.3, react 17, react-native
The text was updated successfully, but these errors were encountered:
thanks for the report; I made a quick workaround in 1.1.4 and will fix this for real later -- note that in 1.1.4 no memoization actually occurs (it is rendered each time, regardless of props) -- see the tests here 5482de9#diff-7cf99adf8ee22020366a84d2a751bccf8fc3e43029c9df2e7c75b2d72c8213d0 (note the skipped test as well)
Want to say, this library is great.. maybe i'll find time to dive in and try to work this out myself, but if not:
Inlining function components wrapped in memo() returns this error:
When not inlining, they appear as <undefined ...> in toString() output.
It'd be great to support them if it's a simple thing!
isolate-components v1.1.3, react 17, react-native
The text was updated successfully, but these errors were encountered: