-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
[Bug]: <title>Error: object 'validate_standard_inputs' not found #730
Comments
@kaipingyang could you start with a new session and load |
1.linux system install development version of teal:
3.Windows system install development version of teal:
4.Windows system install https://github.com/insightsengineering/depository 2022 _10_13 release version:
|
@mhallal1 The bug should be caused by the absence of Thus the Please check the document at https://github.com/insightsengineering/teal.modules.clinical/blob/main/NAMESPACE |
@kaipingyang the function |
Sorry to be late to the party, I thought the lack of reproduction by @BLAZEWIM was conclusive. @mhallal1 is correct, this is an internal function. @kaipingyang, did your problem occur when you were using a module or creating one? |
|
If you run |
If
This should be fixed. @shajoezhu I'm going to leave this to you and let SME make any changes |
wiil do! Thanks @nikolas-burkoff |
|
What happened?
Error: object 'validate_standard_inputs' not found
Most modules use
validate_standard_inputs
to check variables,such asIn teal.modules.clinical version 0.8.14.9021 we can query the
help(validate_standard_inputs)
for the validate_standard_inputs function, butThe validate_standard_inputs object is not found when we enter
![image](https://user-images.githubusercontent.com/55199277/221088927-f5d93643-ba00-4dbb-9eb9-e872e97151dd.png)
validate_standard_inputs
When running the example given in the validate_standard_inputs help, an error appears on the shiny app because the validate_standard_inputs object is not found:
sessionInfo()
Relevant log output
Code of Conduct
Contribution Guidelines
Security Policy
The text was updated successfully, but these errors were encountered: