Related to #31 , the input$my_input_id reference in Shiny initializes as NULL. The values are inaccessible until onSort is called at the first client interaction.
In most cases this will not be a problem, but it could potentially cause some issues in downstream reactivity if the "current state" of the DOM is desired before onSort has fired. Would be nice if the client fired the onSort callback (or had an onInitialize callback) or something of that nature whenever the client finishes initializing.
Related to #31 , the
input$my_input_id
reference in Shiny initializes as NULL. The values are inaccessible untilonSort
is called at the first client interaction.In most cases this will not be a problem, but it could potentially cause some issues in downstream reactivity if the "current state" of the DOM is desired before
onSort
has fired. Would be nice if the client fired theonSort
callback (or had anonInitialize
callback) or something of that nature whenever the client finishes initializing.