Feature: allow keywords too in multi-queries #400
Merged
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
This feels more idiomatic when using this from Clojure or w/ EDN requests in http-api-gateway. Strings are still allowed too.
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.
...but still allow strings too. This is in the "query labels" top-level keys that are used to associate the responses with their respective queries.
This feels more idiomatic when using this from Clojure or w/ EDN requests in http-api-gateway. Strings are still allowed too.
Fairly small thing either way. Any reason not to allow this?
I ran into this when writing multi-query endpoint tests in http-api-gateway.
I threw a couple other small things I noticed while I was in here too, but let me know if you think anything should be reverted or split out of this PR.