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

Restrict the scope of interactivity for gr.Dataframe #2020

Closed
Tracked by #1201
GuillemGSubies opened this issue Aug 16, 2022 · 2 comments · Fixed by #10734
Closed
Tracked by #1201

Restrict the scope of interactivity for gr.Dataframe #2020

GuillemGSubies opened this issue Aug 16, 2022 · 2 comments · Fixed by #10734
Assignees
Labels
💾 Dataframe enhancement New feature or request

Comments

@GuillemGSubies
Copy link

Is your feature request related to a problem? Please describe.

Sometimes I want the user to be able to modify some part of the Dataframe, however it can be problematic if they modify something that they shouldn't.

Describe the solution you'd like

It would be great if it were possible to tell the constructor what parts can be modified, instead of just allowing everything to be changed.

@abidlabs
Copy link
Member

Hi @GuillemGSubies at what level would you want to scope this? At a per-column level or at a per-cell level?

@abidlabs abidlabs added the enhancement New feature or request label Aug 16, 2022
@GuillemGSubies
Copy link
Author

For my use case, a per column level. However I think the implementation would make sense if the input was a view of the dataframe, so it is more flexible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💾 Dataframe enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants