This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
Add option to configure the format of linter messages #47
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
|
Beautiful, will test and merge soon. |
steelbrain
added a commit
that referenced
this pull request
Aug 7, 2015
Add option to configure the format of linter messages
|
👍 When will this change show up in apm? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is an alternative prospective fix for #28. It adds a new string setting,
messageFormatwhich can contain format specifiers for the full Pylint message (%m), the message ID (%i) and the message symbol/human-readable ID (%s). The default value is set to%mwhich means the current default behaviour would be maintained.This is similar to what status-bar does for formatting the cursor position. I think its nice for packages to not be too opinionated on how it should format things like this.
This PR would supersede #43.
This change is