Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add row level access control #8

Merged
merged 6 commits into from
Jan 30, 2025
Merged

feat: add row level access control #8

merged 6 commits into from
Jan 30, 2025

Conversation

JasperSch
Copy link
Collaborator

@JasperSch JasperSch commented Jan 28, 2025

Allow or deny edits/deletes per row

Resolves feature request: #7

Shorter delay when modifying large datasets.

Slightly slows down initial loading of the data (since logic for each row needs to be evaluated on whether or not to add buttons). However the user experience is generally better because of the above improvement.

Allow or deny edits/deletes per row

Change-Id: Ie17e70ac51327c68973f3821bccf59b9bceb1e1b
Change-Id: Iebb51b0e154c5a3ceb451e53b268c3ca71d65753
More logical since input data is expected to be tibble. When
implementing custom canEditRow() and canDeleteRow() logic, tibble is
therefore the expected data type.

Change-Id: I53b7346f737c817ff4e0379b3d567740baf7ad49
- Always allow to modify / delete newly inserted rows
- Allow to pass on boolean values

Change-Id: I552a7a31babb554bcd7aeb6337b19fd6d76968e3
Gives a more consistent user-intuitive look.
@JasperSch JasperSch merged commit a4deeb1 into main Jan 30, 2025
6 checks passed
@JasperSch JasperSch deleted the row_button_control branch January 30, 2025 13:47
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