-
Notifications
You must be signed in to change notification settings - Fork 69
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
Please consider treating datagrids as inputs as well as outputs ? #1560
Comments
Related - Add ability to update cells and data from the server: #1449
Correct. As of v1.0.0, this is not implemented. (But it could be in the future! Will expand on this in followup comment)
We already have the ability to edit a data frame within the browser via a single cell edit. The current approach has been:
We can access the updated data via
It is definitely different as updates are happening to the rendered output after the initial rendering has occurred. But if the decorated
|
Questions I run into with pasting data:
On the server side, we can get pretty far with
Goal: Reduce this question set . Any thoughts or approaches appreciated! |
This is half a feature request, half a question about how shiny conceptualizes data input.
I'd like to use shiny to help my researcher colleagues process some analytical data. Because most of the potential users are not proficient coders, the most accessible/realistic way to input data should be copy-and-paste from a spreadsheet app into the shiny app. Pasting into an editable datagrid does not appear to be currently implemented, and the fact that DataGrid is explicitly defined as an output makes me wonder if my use case is at odds with some core philosophy of shiny, such as "input data resides on the server", or "input data must be uploaded from a file".
My two cents: pasting into a datagrid offers at least two benefits over simply pasting data into a text area: (a) because any problems in formatting/cell mismatches are immediately apparent, the user can easily perform some kind of visual data validation; (b) one thing end-users frequently mistype is column headers; this problem disappears if the headers are already specified by a datagrid input.
So, is it possible that datagrids will some day be treated as full-blown inputs, or would that break things and/or go against some core conceptualization of py-shiny?
The text was updated successfully, but these errors were encountered: