Skip to content

perfs: do not add features and filters in data browser DOM until user use them#3165

Merged
yohanboniface merged 7 commits into
masterfrom
browser-open-perfs
Jan 27, 2026
Merged

perfs: do not add features and filters in data browser DOM until user use them#3165
yohanboniface merged 7 commits into
masterfrom
browser-open-perfs

Conversation

@yohanboniface

Copy link
Copy Markdown
Member

No description provided.

yohanboniface and others added 7 commits January 21, 2026 19:04
When opening the data browser (left panel), the DOM is huge, so let's
clean it, not to clutter memory

Co-authored-by: David Larlet <david@larlet.fr>
Filters can be huge, so let's not polute the DOM pointlessly

Co-authored-by: David Larlet <david@larlet.fr>
When there are a lot of features and/or a lot of datalayers,
this can make the DOM huge.
The DOM will also be computed when some filter is active (so
we can compute the current/total count).

Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
We have two form classes:
- Form, used for imports, filters…
- MutatingForm, used for data manipulation

Only this later is synced (to other peers), so no need to have a
debounce for the former.
We could even make this debounce more smart in a later step, by
only activating it when the map is actually in sync mode, otherwise
we do not need it either (and it slows down tests…).

Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
@yohanboniface yohanboniface merged commit 60c4d7f into master Jan 27, 2026
3 checks passed
@yohanboniface yohanboniface deleted the browser-open-perfs branch January 27, 2026 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant