You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ui_module_check_xyz() - empty fun (we can even don't create it at all)
check_xyz() - for custom checks - only if needed, function returning TRUE if ok else error message (similar to checkmate)
test_xyz() - for custom checks - only if needed, function returning boolean (similar to checkmate)
Extra:
I do expect quite a few module_check_xyz() functions, e.g. module_check_reactive(), module_check_tryerror(), module_check_shinysilenterror(), module_check_qenverror. Instead of exporting a lot of objects, we might create a factory to create them dynamically if needed. (or both?)
The goals it to have a functionality that is:
testable
extendable - e.g. one validate module calling another validate module
returning consistent validation errors
The use cases:
teal:::srv_validate_reactive_teal_data
teal modules (I assume this is going to be exported)
The text was updated successfully, but these errors were encountered:
(please note that the below is just a rough design - feel free to adapt if needed)
module_validate_xyz()
- a shiny module executing validation:srv_validate_xyz(x)
- it does the following:ui_validate_xyz()
- display error message:module_check_xyz()
- a shiny module executing checks:srv_module_check_xyz()
- returns reactive with theAssertCollection
object (see: https://mllg.github.io/checkmate/reference/AssertCollection.html)ui_module_check_xyz()
- empty fun (we can even don't create it at all)check_xyz()
- for custom checks - only if needed, function returning TRUE if ok else error message (similar tocheckmate
)test_xyz()
- for custom checks - only if needed, function returning boolean (similar tocheckmate
)Extra:
I do expect quite a few
module_check_xyz()
functions, e.g.module_check_reactive()
,module_check_tryerror()
,module_check_shinysilenterror()
,module_check_qenverror
. Instead of exporting a lot of objects, we might create a factory to create them dynamically if needed. (or both?)The goals it to have a functionality that is:
The use cases:
teal:::srv_validate_reactive_teal_data
The text was updated successfully, but these errors were encountered: