Make input_selectize work correctly within a module

[jcheng5]

TODO

• Automated test

Description

User adam_pinky reported this on Discord:

Hi team, we found a regression upgrading to shiny v0.7.0. The really useful input selectize multiple choice ui element no longer renders correctly. It shows only as a list. Interestingly, this behaviour only appears to occur when using shiny modules.

Could the team confirm whether there is any workaround or if we are using the modules incorrectly for v0.7.0?

Repro

import shiny


@shiny.module.ui
def module_ui() -> shiny.types.NavSetArg:
    """Build module 1 UI"""
    return shiny.ui.nav_panel(
        "module1",
        shiny.ui.input_selectize(
            "id",
            "labels",
            [1, 2, 3, 4],
            multiple=True,
        ),
    )


@shiny.module.server
def module_server(app_input: shiny.Inputs, output: shiny.Outputs, _) -> None:
    """Build Module 1 Server"""


def server(_, __, ___):
    """Shiny main server"""
    module_server("module1")


UI = shiny.ui.page_navbar(
    module_ui("module1"),
)

app = shiny.App(UI, server)

https://shinylive.io/py/editor/#code=NobwRAdghgtgpmAXGKAHVA6VBPMAaMAYwHsIAXOcpMASxlWICcyACAZwAsaJsAdCfvwACnbtgwxiAEwCuAGzgYZNflLgAzFpNkKA+soAUAShYBaAHzsuPDGWyo4bDADkoANwDKcMgEFGAc0R+FhCWXjBw8IAhZTkpLWl5OBYARhYAVQBJSIiIiFCWRm8ZRnzRG2UMaDddVCgIODkDYILQ8O0klPC8FtarMSUaDG5UGTJdNka4QjIaAC84Zvy+1vCaKW7elZDwuSgAI0a2TeXtkOAUvBYAJiuAZiuAFgBdHtOzmHlZ1AUAXgAVRgyOBvbZGUGhIyCAQQETWcQdBQYSaMNxwRiqDQJHRwCbotGMAxoVC6EZjRD9GyZCCjMhsK7EMa0inlcQAeSZY3pLF0JgsLGcpDgQXeOWisXiAFlEgpUiwvKj0WK8tC1JoUQSDLorrptTzdUYRQVlR54VooNx2PilblIu9EbiNejmmAHV0wFCYfwsixfpTxJU6v5cdV9lBCVsHfoaC63eFwfxPfxib7-RgfOgDFkrk7GJ6wABfZ5AA

[adampinky85]

thanks @jcheng5 much appreciated!

[schloerke]

This feels off to me. I'd like double check this in the morning before we merge the PR.

Everything else is great!

[schloerke]

Yup. To my knowledge, selectize.js changed how it stores options / selected values.

Either way, if we would have used the correct selectize testing class, the error would have been surfaced earlier.

Yes, we should do this in a followup PR as the changes are not related to this Issue