Fixed GetRangeAsync not having correct optional parameters #1201
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
Second attempt at fixing the linter, apologies for the initial fix. I mean, obviously fixing code using Anydesk remotely was just a stroke of my genius.
Dionysusnu
suggested changes
Mar 5, 2024
Co-authored-by: Dion <39664950+Dionysusnu@users.noreply.github.com>
When the Syntax Strikes Back, We Strike Back Harder. Co-Authored-By: Dion <39664950+dionysusnu@users.noreply.github.com>
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.
Hello,
according to the docs, the
GetRangeAsyncshould haveexclusiveLowerBoundandexclusiveUpperBoundas optional parametrs, while currently that's not the case.