Python: Add precision to NoSQL query #15720
Merged
Conversation
This file contains hidden or 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
Due to this, it was not part of any query suite :O
Contributor
Yes. I read through the old PR to jog my memory. I think 'high' should be defensible. |
Contributor
|
Do we need a change note about this query now being included by default? Thanks for cleaning up this mess! |
Member
Author
sure, I made one 👍 I based it on the following, but put emphasis on the fact that it's run by default now 😅 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Due to this, it was not part of any query suite :O
@yoff do you agree it should be
high, or should it bemedium? I don't have the details from when you did the promotion of this query, so just took a guess.