Vedha Viyash

I do see benefits of a vignette like "How to use teal" which would be similar to the [getting started vignette](https://insightsengineering.github.io/teal/main/articles/getting-started-with-teal.html) but strictly from a usage perspective. In the video...

I'm not sure what you mean by "invisible inputs" but if you're referring to the bottom right `Computing ...` which is the only `conditionalPanel` UI I can see over here...

> Should we make this as widget in teal.widget ? If you're proposing just the `custom_modal_dialog` then it makes perfect sense to me. But nothing more than that because in...

> I'm not sure I like invisible inputs. But then that is what conditinalPanel does and we have a lot of those in the modules. I don't like when the...

> should we consider adding tabs in modal ? How about moving it to the top? and having a scroll to the table as suggested [here](https://github.com/insightsengineering/teal.slice/issues/394#issuecomment-1721160586)

> what happens if we decide to take it out at some point? You're right, Removing the modal is an effect of being inside the modal which is the intended...

While debugging this reactivity issue I feel like there are additional redundant reactivity triggered even when the state is empty because by default `observeEvent` has `ignoreInit = FALSE`and `ignoreNULL =...

I suspect that this might be harder than just cutting off reactivity. I believe that the root cause of the issue is not because of unwanted things being observed but...

A little curveball, What if the module takes in a `teal_slice` object? When it is not passed the global `teal_slice` from init is used. This should open up many possibilities...