VisActor / VisActor/VTable

[Bug] 搜索组件SearchComponent,数据量大时,搜索卡顿严重

Open
#4,695 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Version

1.22.3

Link to Minimal Reproduction

搜索组件SearchComponent,数据量大时,搜索卡顿严重

Steps to Reproduce

import { SearchComponent } from '@visactor/vtable-search';

Current Behavior

搜索组件SearchComponent,数据量大时,搜索卡顿严重

Expected Behavior

搜索组件SearchComponent,数据量大时,搜索卡顿严重

Environment
- OS:
- Browser:
- Framework:
Any additional comments?

No response

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 at the SearchComponent entry point from @visactor/vtable-search and reproduce the lag with a large dataset. Review how searches are triggered and measured in the component, then verify completion by confirming that searching remains responsive with large data while preserving the expected results.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.