Stabilize how required resources (i.e. normalizers) are constructed #229
Labels
priority:low
Low priority
technical debt
A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup"
It'd be good to avoid hard-coding too much, and let those resources manage the responsibility of checking env vars, etc. We should allow a constructed normalizer query handler to be passed through if it's already been declared, but otherwise, we ideally should be hands-off about how params are managed and passed.
Because there are some shared resources (e.g. Variation uses Gene) we need to make sure that this can be done in a composable manner, which could be tricky.
The text was updated successfully, but these errors were encountered: