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

Update for Linter v2 #12

Merged
merged 12 commits into from
Mar 22, 2017
Merged

Update for Linter v2 #12

merged 12 commits into from
Mar 22, 2017

Conversation

Arcanemagus
Copy link
Member

@Arcanemagus Arcanemagus commented Mar 21, 2017

Update to work with Linter v2. Creates a UI provider for Linter v2 so it will feed us all the messages, allowing us to manage the markers ourselves instead of trying to intercept the markers from Linter.

I'm not sure what the previous configuration was, as the versions
weren't defined in the package.json, but it looked ancient. Update to
the current style guide used in most other projects in this org.
Move the configuration to a configSchema key in package.json so Atom
doesn't have to parse and run the package code to know what settings are
available for it.
Update the minimap consumer code to match the current practices.
@Arcanemagus
Copy link
Member Author

Note, as far as I can see from debugging this, it should be working, but no markers are showing up in the minimap and I'm not entirely sure what is wrong.

@Arcanemagus
Copy link
Member Author

With some help from @abe33 on how minimap gets the styles for the decorations, this is now working locally! Fixing up a few more things...

Provide a Linter "UI" so we are given all new messages from the Linter.
Using these messages, generate markers of our own and decorate them with
minimap.
let editor;
let minimap;

beforeEach(() => {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

import { beforeEach } from 'jasmine-fix'

and then you'll be able to do beforeEach(async function(){

If a user somehow doesn't already have Linter installed when they
installed this package, install it for them. Mainly added to bring in
the requirement of Linter v2 as this package will no longer work with
Linter v1 after this gets released.
As these classes are just being used for the color, and can be used on
multiple different marker types, simplify the name a bit.
IANAL so I have no idea if "AtomLinter" works for the name.
* Specify the full path to the main file
* Update the description
* Fill in some keywords
* Mark as private to prevent accidental NPM publishings
Add specs testing that the package properly registers itself with Linter
and Minimap, and handles messages as expected.
Add a configuration for CircleCI builds.
Linter fixed a bug in v2.1.1 so now newly added UI providers are given
any messages registered before they were activated as their first
`added` batch. This means we can always just use `added` and `removed`.
Copy link

@steelbrain steelbrain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good and should work

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.

2 participants