Upgrade to SublimeLinter4 #2
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
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.
Hello,
SublimeLinter4 has been stable for > 2 years now, with SublimeLinter3 being deprecated. I wanted to use this plugin with SublimeLinter4, so went about upgrading it.
The major changes are:
configsetting instead of the defaultargs, which felt ambiguous due to the need for both executable args as well as program args.setup.cfgfor project linting configuration, instead of the deprecated.sublimelinterrcREADME.mdfor enhanced clarityOtherwise I attempted to keep the functionality the same, namely implementing custom logic to find
scalastyle-config.xmlin parent directories, since the previously built-inconfig_filefunctionality appears to be removed from SublimeLinter 4.Thanks for having a look.