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.

Sign up for GitHub

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

Jump to bottom

Better error and warning handling #467

Open
korikuzma opened this issue Jul 18, 2023 · 2 comments
Open

Better error and warning handling #467

korikuzma opened this issue Jul 18, 2023 · 2 comments
Labels
priority:medium Medium priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup"

Comments

@korikuzma
Copy link
Member

Similar to this issue in cool-seq-tool. We should provide both warnings and errors in the response. An example of a warning would be in #176 ["Multiple GRCh38 representations found"]. Error messages will be populated if we were unable to normalize and returned None or Text object in the response.
@korikuzma korikuzma added priority:medium Medium priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup" labels Jul 18, 2023
@korikuzma korikuzma mentioned this issue Aug 1, 2023
Closed
@korikuzma
Copy link
Member Author

This will really help clean up the gnomad vcf to protein code.... too many if/else conditions 🥵

@github-actions GitHub Actions
Copy link

github-actions bot commented Jan 6, 2025

This issue is stale because it has been open 135 days with no activity. This issue will be closed if no further activity occurs in 14 days.

@github-actions github-actions bot added the stale label Jan 6, 2025
@korikuzma korikuzma removed the stale label Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority:medium Medium priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup"
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@korikuzma