Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Rewrite in ES2017 #255

Merged
merged 3 commits into from
Oct 15, 2016
Merged

Rewrite in ES2017 #255

merged 3 commits into from
Oct 15, 2016

Conversation

Arcanemagus
Copy link
Member

@Arcanemagus Arcanemagus commented Oct 15, 2016

Rewrite in ES2017, including:

  • Rename pep8ErrorsToWarnings to pycodestyleErrorsToWarnings
  • Move the range modification code into a separate file
  • Remove most of the range fixers in favor of rangeFromLineNumber's "word" highlighting as it has the same effect in all removed cases.
  • Fix the remaining range fixing code to actually work properly
  • Set the minimum Atom version to v1.9.0 since we have tight version restrictions as we are using unpublic code parts
  • Move the configuration to a configSchema in the package.json
  • Install hacking in CI to test the custom range highlighting as half the code is to deal with issues it presents
  • Observe all settings
  • Use helpers.rangeFromLineNumber where possible
  • Use async/await to simplify the code where possible
  • Fix a race condition where the editor contents have changed since the lint was triggered
  • Convert projectConfigFile to an array. This is largely transparent as it was already being handled like one, this just means Atom handles stripping whitespace for us

Rewrite in ES2017, including:

* Rename `pep8ErrorsToWarnings` to pycodestyleErrorsToWarnings`
* Move the range modification code into a separate file
* Remove most of the range fixers in favor of `rangeFromLineNumber`'s
  "word" highlighting as it has the same effect in all removed cases.
* Fix the remaining range fixing code to actually work properly
* Set the minimum Atom version to v1.9.0 since we have tight version
  restrictions as we are using unpublic code parts
* Move the configuration to a `configSchema` in the package.json
* Install `hacking` in CI to test the custom range highlighting as half
  the code is to deal with issues it presents
* Observe all settings
* Use `helpers.rangeFromLineNumber` where possible
* Use `async`/`await` to simplify the code where possible
* Fix a race condition where the editor contents have changed since the
  lint was triggered
* Convert `projectConfigFile` to an array. This is largely transparent as
  it was already being handled like one, this just means Atom handles
  stripping whitespace for us
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant