Is your feature request related to a problem? Please describe
It is very common to update parameters of components throughout the app usage lifecycle. This is most easily done with the name parameter, but not every component has that parameter. This means new-er users to the framework will learn about updating with the name component: q.page["test"].my_component.content = "hey" but then have no idea what to do when name is not there.
They can ("of course") use the old index method: q.page["test"].items[2].textbox.value="hey" but this is harder and often Wave users that joined after the 1.0.0 release will not know about this.
Describe the solution you'd like
[ ] An audit of all components to make a list of everything that does not have name as a parameter
[ ] Add name as a parameter to all of these
Describe alternatives you've considered
Leave things as is, monitor chats and teach people about the old method
Write new docs with key words that people might find when they try to update things like image
Is your feature request related to a problem? Please describe
It is very common to update parameters of components throughout the app usage lifecycle. This is most easily done with the
name
parameter, but not every component has that parameter. This means new-er users to the framework will learn about updating with the name component:q.page["test"].my_component.content = "hey"
but then have no idea what to do when name is not there.They can ("of course") use the old index method:
q.page["test"].items[2].textbox.value="hey"
but this is harder and often Wave users that joined after the 1.0.0 release will not know about this.Describe the solution you'd like
name
as a parametername
as a parameter to all of theseDescribe alternatives you've considered
image
Additional context
Resolved question: https://github.com/h2oai/wave/discussions/2338