Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question]: qenv.error probably doesn't make sense anymore #1458

Open
3 tasks done
gogonzo opened this issue Jan 20, 2025 · 0 comments
Open
3 tasks done

[Question]: qenv.error probably doesn't make sense anymore #1458

gogonzo opened this issue Jan 20, 2025 · 0 comments
Labels
question Further information is requested

Comments

@gogonzo
Copy link
Contributor

gogonzo commented Jan 20, 2025

What is your question?

#1357 (comment)

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

  • I agree to follow this project's Code of Conduct.

Contribution Guidelines

  • I agree to follow this project's Contribution Guidelines.

Security Policy

  • I agree to follow this project's Security Policy.
@gogonzo gogonzo added the question Further information is requested label Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant