Add setting use_package_names
#52
Open
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
Instead of using the file path as arg which pylint will in turn convert to a package name, we do the conversion on our own. This implementation takes the file path of the view relative to the defined working dir (usually the project path) and then basically swaps '/' with '.'.
|
@kaste still wanna do anything with this? |
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.
Instead of using the file path as arg which pylint will in turn
convert to a package name, we do the conversion on our own.
This implementation takes the file path of the view relative to
the defined working dir (usually the project path) and then basically
swaps '/' with '.'.
Fixes #36
Feel free to bike-shed the name of the setting.