Fix truncated copy/paste in database_specific description #229
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
Adds back the `as defined by the database` in the description of the `range` object's `database_specific` field. This brings it into line with the descriptions of the other two `database_specific` fields Signed-off-by: Chris Bloom <chrisbloom7@github.com>
oliverchang
approved these changes
Mar 15, 2024
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.
Adds back the
as defined by the databasein the description of therangeobject'sdatabase_specificfield. This brings it into line with the descriptions of the other twodatabase_specificfields. I suspect it was just a bad copy/paste operation as we were adding those fields to other objects beyond the top level.