VisActor / VisActor/VTable

透视表更新颗粒度控制能精细一点吗

Open
#4,669 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.7k
Forks
486
Avg merge
1d 19h
Merged PRs (30d)
16

Description

每次调用 updateOption 在调用链路中都会调用 createSceneGraph,这里的 this.proxy.createGroupForFirstScreen 是否可以做缓存对比来按需更新呢

https://github.com/VisActor/VTable/blob/fb457001fd368191ddf65e44d5b3aeb596b15c4a/packages/vtable/src/scenegraph/scenegraph.ts#L409-L461

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with packages/vtable/src/scenegraph/scenegraph.ts at createSceneGraph (the linked lines), then trace how updateOption reaches it and how this.proxy.createGroupForFirstScreen is used. Determine when the existing scene needs updating versus when the group can be reused; done means unnecessary scene-graph work is avoided without changing update behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, performance
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.