Aleksander Chlebowski

An early version of `teal::validate_inputs` was able to pass `errorClass` to `shiny::validate`. This is now not possible because `...` only takes validators but a special argument can be added. Then...

Funnily enough, when I run the example app from `tm_missing_data`, the "By Variable Levels" tab does not seem to capture validator messages at all. 

I think the dispatch works as intended, actually. The generic dispatches on the class of `modules`, not `id`: ``` srv_nested_tabs

On the other hand, the `default` method only raises an error, so in principle it should not need a default value for `reporter`.

That's not quite enough information, @npaszty. What version of tmc are you using? Your `sessionInfo` suggests a vanilla session. Can you provide the application code?

All right. We are in the midle of releasing core `teal` packages to CRAN. `teal.data` was just published, actually :champagne: :partying_face: `teal.slice` and `teal` will soon follow (this coming February)....

OK then. If you find you can't afford to properly rebuild modules, you can use `teal::as_tdata` as a temporary measure.

> we built mostly custom modules Sorry if I misunderstood.

Now I get it :+1:

> I believe @chlebowa was just using the example code in the function's roxygen doc. Correct.