insightsengineering / insightsengineering/teal
[Question]: qenv.error probably doesn't make sense anymore
- Dominant language
- R
- Stars
- 263
- Forks
- 59
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 5
Description
### What is your question?
https://github.com/insightsengineering/teal/pull/1357#discussion_r1841704759
After introducing decorators in teal.modules.general and teal.modules.clinical it doesn't make sense to handle `qenv.error` anymore (is it?). `qenv.error` was made to avoid shiny.error and to handle some things gracefully - to still be able to call `eval_code` or `get_code` without any strange errors (get_code(). We need to investigate if `qenv` still makes sense.
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct.
### Contribution Guidelines
- [x] I agree to follow this project's Contribution Guidelines.
### Security Policy
- [x] I agree to follow this project's Security Policy.
Contributor guide
Assessment
This issue has not been assessed yet.