Bug: Handle null values in slice() with multiple arguments#2554
Open
bigshika wants to merge 1 commit intoblacksmithgu:masterfrom
Open
Bug: Handle null values in slice() with multiple arguments#2554bigshika wants to merge 1 commit intoblacksmithgu:masterfrom
bigshika wants to merge 1 commit intoblacksmithgu:masterfrom
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
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.
I ran into a bug where I had two notes:
If I run:
Both notes are returned.
If I run:
Only Test2 is returned.
This behaviour persists even if there's a null check involved on the property. My expectation is that the number of notes returned by the first and second queries would be the same.