daattali/shinywc issues and pull requests

#29 - When using nested components, events don't work

Issue - State: closed - Opened by daattali over 3 years ago - 1 comment

#28 - Component doesn't render properly when a named slot contains multiple other components

Issue - State: closed - Opened by daattali over 3 years ago

#27 - For get/set properties, remove the suffis `prop` from the functions, since attributes are now active bindings

Issue - State: open - Opened by daattali over 3 years ago

#26 - Attributes not working when rendering with uiOutput+renderUI

Issue - State: closed - Opened by daattali over 3 years ago

#25 - Explore using R6 active bindings

Issue - State: closed - Opened by daattali almost 4 years ago - 1 comment

#24 - Try to abstract the Proxy R6 class so that less code is required in the components

Issue - State: closed - Opened by daattali almost 4 years ago - 1 comment

#24 - Try to abstract the Proxy R6 class so that less code is required in the components

Issue - State: closed - Opened by daattali almost 4 years ago - 1 comment

#23 - Some properties are read-only

Issue - State: closed - Opened by daattali almost 4 years ago - 2 comments

#22 - Explore different design: instead of each component containing all the R/JS files, have the core functions abstracted away in a common package and the component only calls functions in the package

Issue - State: closed - Opened by daattali almost 4 years ago - 1 comment

#21 - Automate the creation of the R files based on a schema file

Issue - State: open - Opened by daattali almost 4 years ago - 1 comment

#21 - Automate the creation of the R files based on a schema file

Issue - State: open - Opened by daattali almost 4 years ago - 1 comment

#20 - Schema needs to define the parameters for methods (just the names or number of arguments)

Issue - State: closed - Opened by daattali almost 4 years ago - 1 comment

#19 - Some attributes are "write-only"

Issue - State: closed - Opened by daattali almost 4 years ago - 2 comments

#18 - Fix get/set of attributes to actually use attributes instead of properties

Issue - State: closed - Opened by daattali almost 4 years ago

#17 - Support get/set properties

Issue - State: closed - Opened by daattali almost 4 years ago

#16 - Bug: component cannot be rendered from a `insertUI`

Issue - State: open - Opened by daattali almost 4 years ago - 2 comments

#15 - Try to convert component to an htmlwidget

Issue - State: closed - Opened by daattali almost 4 years ago

#14 - Bug: when multiple knobs are on a page, sometimes can't modify the knob with the mouse

Issue - State: closed - Opened by daattali almost 4 years ago - 1 comment

#13 - Bug: component cannot be added to a page dynamically without having one on init

Issue - State: closed - Opened by daattali almost 4 years ago - 3 comments

#12 - Components should work in shiny modules

Issue - State: closed - Opened by daattali almost 4 years ago

#11 - Bug: when a named slot is used but no default slot is given, a whitespace is used as default slot

Issue - State: closed - Opened by daattali almost 4 years ago

#10 - Can a default slot always be used, or can a custom element define that it doesn't support a default unnamed slot?

Issue - State: closed - Opened by daattali almost 4 years ago - 1 comment

#9 - Ensure default slot works even when other parameters are not used

Issue - State: closed - Opened by daattali almost 4 years ago

#8 - Should user be able to add extra attributes (such as standard global html attributes) to a custom element?

Issue - State: closed - Opened by daattali almost 4 years ago

#7 - Look into providing a "save" functionality that asks the component to return all the important values

Issue - State: closed - Opened by daattali almost 4 years ago - 2 comments

#6 - Adhere to a better json schema

Issue - State: closed - Opened by daattali almost 4 years ago - 1 comment

Ecosyste.ms: Issues

GitHub / daattali/shinywc issues and pull requests

#29 - When using nested components, events don't work

#28 - Component doesn't render properly when a named slot contains multiple other components

#27 - For get/set properties, remove the suffis `prop` from the functions, since attributes are now active bindings

#26 - Attributes not working when rendering with uiOutput+renderUI

#25 - Explore using R6 active bindings

#24 - Try to abstract the Proxy R6 class so that less code is required in the components

#24 - Try to abstract the Proxy R6 class so that less code is required in the components

#23 - Some properties are read-only

#22 - Explore different design: instead of each component containing all the R/JS files, have the core functions abstracted away in a common package and the component only calls functions in the package

#21 - Automate the creation of the R files based on a schema file

#21 - Automate the creation of the R files based on a schema file

#20 - Schema needs to define the parameters for methods (just the names or number of arguments)

#19 - Some attributes are "write-only"

#18 - Fix get/set of attributes to actually use attributes instead of properties

#17 - Support get/set properties

#16 - Bug: component cannot be rendered from a `insertUI`

#15 - Try to convert component to an htmlwidget

#14 - Bug: when multiple knobs are on a page, sometimes can't modify the knob with the mouse

#13 - Bug: component cannot be added to a page dynamically without having one on init

#12 - Components should work in shiny modules

#11 - Bug: when a named slot is used but no default slot is given, a whitespace is used as default slot

#10 - Can a default slot always be used, or can a custom element define that it doesn't support a default unnamed slot?

#9 - Ensure default slot works even when other parameters are not used

#8 - Should user be able to add extra attributes (such as standard global html attributes) to a custom element?

#7 - Look into providing a "save" functionality that asks the component to return all the important values

#6 - Adhere to a better json schema

#5 - Create separate functions for all properties/methods instead of `inputknob_set_attr`/`inputknob_call`

#4 - Bug: multiple components on the same page, only the first one works

#3 - Look into creating a demo shiny app for a component automatically

#2 - Some methods can have return values

#1 - Some attributes can be required