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

Legacy support for multi and search routes #218

Closed
alancleary opened this issue Jul 9, 2019 · 1 comment
Closed

Legacy support for multi and search routes #218

alancleary opened this issue Jul 9, 2019 · 1 comment
Assignees

Comments

@alancleary
Copy link
Contributor

The search route should redirect to a genes route with the single gene-source pair as the target. Since the multi route doesn't require a source, it should redirect to the new search route, which, assuming the genes entered exist in one or more of the sources listed in the config, should redirect to the new genes route once each gene's source has been resolved.

@alancleary
Copy link
Contributor Author

Implemented in commit f441f14.

Note: the multi route actually redirects to the unified gene route (instead of a search as originally described) with every gene added to every source's matrix parameter list. This provides the same functionality as the deprecated multi route but is more verbose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant