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
Currently there are 3 tests in teal and 2 shinytest2 tests in teal that cover decorators. Even though the main functionality is implemented in teal, actual usage and some customization is provided at modules packages. Should we extend modules packages tests (like in tmg/tmc) to cover decorators usage? Those module packages have some custom functions for decorators specification that do not exist in teal, hence the reason to test them there.
Decorators should be tested in teal.modules.*. teal doesn't execute decorators as they are included through ui_args and server_args. teal can't guarantee if decorator returns correct object - it is impossible unless we introduce the design in which decorator would check itself (is it possible?)
What is your question?
Currently there are 3 tests in
teal
and 2 shinytest2 tests inteal
that cover decorators. Even though the main functionality is implemented inteal
, actual usage and some customization is provided at modules packages. Should we extend modules packages tests (like in tmg/tmc) to cover decorators usage? Those module packages have some custom functions for decorators specification that do not exist inteal
, hence the reason to test them there.Some examples to be used for tmg:
The text was updated successfully, but these errors were encountered: