Autocomplete fix #275
Merged
Autocomplete fix #275
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…plus in-taxon vs in-taxon-label fix that probably exists in another branch too
✅ Deploy Preview for monarch-app ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
glass-ships
approved these changes
Aug 12, 2023
kevinschaper
added a commit
that referenced
this pull request
Aug 22, 2023
Fixes #272 Takes care of an errant default start/offset of 1, which skipped the first result in autocomplete queries Also fixes in_taxon vs in_taxon_label mismatch in the cli. (Which I thought I'd fixed and gotten into main, but it might be sitting in an unrelated PR)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #272
Takes care of an errant default start/offset of 1, which skipped the first result in autocomplete queries
Also fixes in_taxon vs in_taxon_label mismatch in the cli. (Which I thought I'd fixed and gotten into main, but it might be sitting in an unrelated PR)