alibaba / alibaba/formily

[Bug Report] Uncaught Error: autorun.memo must used in autorun function body

Open
#4,282 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
12.6k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

- [ ] I have searched the [issues](https://github.com/alibaba/formily/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/currying-dawn-283wsx)

### Steps to reproduce
@formily/core, @formily/react版本为2.3.3
@formily/antd 版本为2.3.1 混合使用容易出现异常
codesandbox加载异常缓慢,具体可查看stackblitz示例:https://stackblitz.com/edit/vitejs-vite-gnrdpaap?file=package.json
直接看console报错,如果版本都替换为2.3.3则正常渲染schema的title

### What is expected?
正常展示json-schema节点

### What is actually happening?
@formily_react.js?v=f13117a4:3288 Uncaught Error: autorun.memo must used in autorun function body.
at autorun.memo (@formily_react.js?v=f13117a4:3288:11)
at @formily_react.js?v=f13117a4:3863:17
at chunk-HRNPGPLR.js?v=e37f71bb:8216:11
at chunk-HRNPGPLR.js?v=e37f71bb:3202:25
at boundary (chunk-HRNPGPLR.js?v=e37f71bb:3184:19)
at chunk-HRNPGPLR.js?v=e37f71bb:3201:14
at reaction2 (chunk-HRNPGPLR.js?v=e37f71bb:3604:9)
at autorun (chunk-HRNPGPLR.js?v=e37f71bb:3628:3)
at chunk-HRNPGPLR.js?v=e37f71bb:8213:30
at Array.forEach ()

### Package
@formily/core@2.3.3

---

Contributor guide

Open the contributing guide

Research direction

Open the linked StackBlitz reproduction and inspect its package.json, then compare the @formily/core, @formily/react, and @formily/antd versions shown in the report. Confirm the console error and verify that the schema title renders normally when the dependency versions are aligned.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.