-
-
Notifications
You must be signed in to change notification settings - Fork 118
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
asis
parameter of shinyjs functions doesn't work for reset()
#146
Comments
Closing because I'm removing the |
The |
For your consideration: Anyone using shiny modules HAS to be aware of the namespace ns()! This is one of the core tenets of using modules and what allows module re-use! You have to write ALL your module code with this in mind. Otherwise you are circumventing the intended use (and could just source() separate .R files if you are just looking to break a large app into pieces). For those of us who want to actually re-use modules as intended, the "assumption" of namespace is not good. I realize you don't want to break all the code out there that already uses shinyjs/modules (even if they are doing it wrong;), but for concept/consistency it really should be on the programmer to pass the correct ns() in their references. This was the main reason I dropped shinyjs for a while b/c it wouldn't work as expected (with modules) and it wasn't readily apparent why. I realize the "asis" is meant to provide both options, but just having to think about shinyjs module code differently than other module code is not ideal. Anyway, I can see the need for backward-compatibility so maybe "asis" is what we have for now. But, I would seriously consider deprecating the way this works in favor of aligning with the way all module code should be written and a programmer doesn't have to take special note to NOT include ns() (or use "asis") when dealing with shinyjs. [Which is a GREAT package BTW. Much needed and appreciated!] |
@sdrumwr I feel like your comment is more appropriate for #118 than this issue? I certainly understand your point about the fact that people who use modules need to know how modules and namespaces work. However, I don't see why the current behaviour is so bad. With shiny modules, the |
related to #118 but only one function doesn't work
The text was updated successfully, but these errors were encountered: