Create an extra test for constants that are not strings #1394
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
- Extra test to cover the case of a constant not being a str Signed-off-by: Jim.Idle <[email protected]>
|
@jimidle This is a zero-diff pr |
|
Hmm - the extra test must already have made it in. |
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.
Changes
While the DBFS linter successfully detects DBFS references in string constants, there was no test to cover the case when a constant is not, in fact, a string. An extra test has been added to increase coverage to 100%.
Linked issues
Resolves #1104
Functionality
databricks labs ucx .........Tests