fix: do not warn for missing filename if connection is a function #6136
+1
−1
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.
If a connection function is used for sqlite3, it warns that the filename is missing even though once the connection function resolves to an object, the filename actually exists.
This PR just assumes if you're using a connection function you know what you're doing. But we could go further and warn in acquireRawConnection, but it seems like that could result in multiple warnings in some cases. Is there a better place this warning could go?