-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Deprecate init_chunks #22
Comments
Example 3 is a way we'd like to go. We should remove It will be decided when we would like to address this issue. |
So I agree with @gogonzo although I think it's probably nicer for users to do things like
Instead of |
@nikolas-burkoff yes, we can use |
The scope of this issue is:
|
Candidate to close: new chunks class will have this functionality. |
Yup closing these are deprecated |
init_chunks()
and other wrappers functions likechunks_push()
are designed to work only in nested shiny namespaces, like teal is built.If we put the
init_chunks
and the wrappers to the simply shiny app we will get an error:This error comes from the fact that
session$ns(character(0))
is assumed to never be empty. This is true wheninit_chunks
is used in the nested module so thesession$ns(character(0))
will return some string then. The teal apps are used in such nested namespaces so it works correctly nevertheless the simple shiny apps could not use teal.code chunks wrappers.BTW the
init_chunks
have useless lines of code, looks like there is a test code leaved when it was developed.teal.code/R/chunks.R
Lines 976 to 977 in 93b334f
1 incorrect and 2 correct apps.
App example for the app with using wrappers and get ERROR.
The example app with init_chunks and additional layer in form of a module. This will work correctly.
THe app example with chunks used directly and the app is working correctly.
Discussed with @mhallal1 and @nikolas-burkoff
The text was updated successfully, but these errors were encountered: