-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
tm_g_distribution
always starts with validation error
#823
Comments
If we hide the output until a test is selected, it might obscure the test feature for this module. I think the intention is to encourage users to select a test or to make user aware of the test output/selection. We could also replace the validation with something more informative to highlight the presence of the "Test" feature if we have to remove the output when no test is selected.
Possibly, it would have to be a required argument with a default value from one of the selection here to avoid the validation to trigger when nothing is selected. teal.modules.general/R/tm_g_distribution.R Lines 360 to 378 in 9d193d3
We could add a default value to the |
That's what I meant. The validation message suppresses whatever output would be generated with no selection (probably errors). If the suppression is performed without validation errors, that's fine by me. Would you like me to propose a change? |
What happened?
This is not necessarily a bug but is does interfere in some cases.
tm_g_distribution
starts withTests
* (id = 'teal-main_ui-root-dist_1-module-dist_tests_input'
) unselected, which produces a validation error in the Tests output. This results in a validation error. Since it is impossible to set the theoretical distribution in the module call, this is inevitable.Would it be possible to either
a) blocking the Tests output be achieved without raising a validation error,
b) add an argument to
tm_g_distribution
?(*) probably should be "Test", by the way
sessionInfo()
No response
Relevant log output
No response
Code of Conduct
Contribution Guidelines
Security Policy
The text was updated successfully, but these errors were encountered: