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

Stabilize how required resources (i.e. normalizers) are constructed #229

Open
jsstevenson opened this issue Aug 22, 2023 · 0 comments
Open
Labels
priority:low Low priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup"

Comments

@jsstevenson
Copy link
Member

jsstevenson commented Aug 22, 2023

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.

@jsstevenson jsstevenson added priority:low Low priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup" labels Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:low Low priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup"
Projects
None yet
Development

No branches or pull requests

1 participant