-
Notifications
You must be signed in to change notification settings - Fork 593
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
Allow hs.chooser query to still be forwarded when no matching string exists #3232
Conversation
…in the choices list
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pull request does not contain a valid label. Please add one of the following labels: pr-fix, pr-change, pr-feature, pr-maintenance
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the look of this, and I also wonder if it might be worth adding the query string to the choice
dictionary even when a valid choice exists? That doesn't need to be part of this PR, but we should do the LUA_NOREF
/LUA_REFNIL
checks before merging.
Sorry about the commit/revert, not sure what VSCode was doing there. |
Thanks! Apologies for the slow merging |
This is an example of how to implement this, it works in my local testing.
It adds a method, enableDefaultForQuery which can be passed a bool to allow the query to be returned to the final handler, even when it doesn't match an item on the choices list.