-
Notifications
You must be signed in to change notification settings - Fork 24
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
Index from 1 #18
Comments
I fear this one might be messy and require changes to the underlying |
... unless on the |
@jennybc, as discussed above in #18 (comment), here is how we might handle on the
|
If we did this, I would think this should be optional behind an argument, since translation back to |
Yes that would be great. Definitely agree re: optional. Naming the actual list currently has other unfortunate consequences for how, e.g., purrr operates. This is why I leave so many lists unnamed, when otherwise I would pull a name out of the list itself. But better labelling in the widget would be helpful. |
Personally, I try to minimize arguments to a |
I'd be happy to run the input through a helper first. I don't really expose the listviewer code in the tutorial anyway. |
While we're discussing interface, I've thought that the name |
I really like the idea of |
I have added a |
I've tried Here's before, I which we can see the sub-component names and values? See how all the sub-components are de-expanded now and I would need to click on each one to reveal its single unit of info? Is it possible to have the indexing from 1 and not this other behaviour? |
This does seem to have something to do with running the primary input list through |
Makes sense, I had set the check to Here is my test case.
|
going to close this; please let me know if it should be reopened. Thanks so much for the great idea. |
When using
jsonedit()
on an unnamed list, elements are labelled by index. Could these indices start at 1 for easier translation between the interactive view and the composition of[
,[[
, andmap(my_list, INTEGER)
commands?The text was updated successfully, but these errors were encountered: