Deny support for useColumnNames tedious option
#1416
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
dhensby
force-pushed
the
pulls/config-fix
branch
5 times, most recently
from
84d05a3
to
30fbbe3
Compare
8 tasks
dhensby
force-pushed
the
pulls/config-fix
branch
from
30fbbe3
to
5f68ebf
Compare
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.
What this does:
This throws an error if the
useColumnNamesconnection option is passed via the config object. See #1413. This option causes errors in the library, so throwing here is not a breaking change, it just gives a more helpful error.Users should use
arrayRowModeconfig insteadPre/Post merge checklist: