Skip to content

fix: don't restore selection - #430

Open
timkambic-ngen wants to merge 1 commit into
UpstreamDataInc:masterfrom
timkambic-ngen:fix-dont-restore-selection
Open

fix: don't restore selection#430
timkambic-ngen wants to merge 1 commit into
UpstreamDataInc:masterfrom
timkambic-ngen:fix-dont-restore-selection

Conversation

@timkambic-ngen

Copy link
Copy Markdown
Contributor

Fixes the issue described here: #428

Comment on lines +54 to +59
// Don't restore selection: Select matches row IDs as CSS selectors, and
// device IDs may contain invalid chars (e.g. ":") that abort table init.
stateLoadParams: (settings, data) => {
// biome-ignore lint/performance/noDelete: selection must not be restored
delete data.select;
},

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't this drop the user's selection when the table gets an update (every 3 seconds)? Any chance we can do something to handle those invalid characters (like URL encoding) rather than just deleting the selection?

Comment on lines +44 to +47
stateLoadParams: (settings, data) => {
// biome-ignore lint/performance/noDelete: selection must not be restored
delete data.select;
},

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same idea as above, although much less of an issue as I believe the user table doesn't get updated automatically.

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.

2 participants