Address pylint possible variable use before init errors #286
Conversation
This file contains hidden or 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
…n PR #284. None of them are all that important since we should already have prior checks in place e.g. in configuration init to bail out, but better safe than sorry.
jonasbardino
added this to the
Sharelink improvements and capability extensions milestone
jonasbardino
deleted the
fix/pylint-possible-use-before-init-sftp-sharelink-errors
branch
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.
Add a few variable initializations to address related
pylinterrors in PR #284.None of them are all that important since we should already have prior checks in place e.g. in configuration init to bail out, but better safe than sorry.