Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add settings for the Alex linter #2268

Merged
merged 1 commit into from
Feb 10, 2019
Merged

Add settings for the Alex linter #2268

merged 1 commit into from
Feb 10, 2019

Conversation

m-pilia
Copy link
Contributor

@m-pilia m-pilia commented Feb 2, 2019

The executable for the Alex linter is currently hard-coded as 'alex',
which is an issue given the fact that it conflicts with the Haskell
lexer generator, whose executable is also called 'alex', has been around
a dozen years before the linter, and is packaged in the official
repositories of the major Linux distributions.

This commit adds options to use a local executable for the alex linter
(which is a node package), and an option to set a custom executable.

As side changes:

  • The pattern in the alex handler is made more readable by turnig it
    into a very-magic regex.
  • Alex handles plain text, markdown, and HTML. Specific flags for HTML
    and markdown are provided when instantiating the linters for the
    respective filetypes, while before those formats were treated as plain
    text.

Resolves #1633

The executable for the Alex linter is currently hard-coded as 'alex',
which is an issue given the fact that it conflicts with the Haskell
lexer generator, whose executable is also called 'alex', has been around
a dozen years before the linter, and is packaged in the official
repositories of the major Linux distributions.

This commit adds options to use a local executable for the alex linter
(which is a node package), and an option to set a custom executable.

As side changes:
* The pattern in the alex handler is made more readable by turnig it
  into a very-magic regex.
* Alex handles plain text, markdown, and HTML. Specific flags for HTML
  and markdown are provided when instantiating the linters for the
  respective filetypes, while before those formats were treated as plain
  text.
@w0rp w0rp merged commit 6ebe24b into dense-analysis:master Feb 10, 2019
@w0rp
Copy link
Member

w0rp commented Feb 10, 2019

Cheers! 🍻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants