Extension Roadmap

[spence-s]

As it stands, the xo linter extension works fairly well but is pretty bare bones and needs some fixing up.

current extension:
https://marketplace.visualstudio.com/items?itemName=samverschueren.linter-xo

Immediate goals

• publish v3 under SamVerschueren.linter-xo
  • Can now be used immediately under the soon to be deprecated spence-s.linter-xo extension - this adds support for xo versions 40+ and new features are being rolled out while maintenance changes hands.
  • deprecate installs of spence-s.linter-xo and show message on start up for users to migrate back to SamVerschuren.linter-xo
• support multi root workspaces correctly
• remove any reliance on package.json fields and instead attempt to resolve the library relative to the working folder, and only then error
• enable the extension by default
• add a couple of simple commands to restart and run the extension as requested Now recaches xo after updating on the next file open.
• Configurable debounce which improves large file linting performance
• Code Action quick fixes are now available
• Support format on save "modifications" mode.
• Add tests for the extension, CI, automated releases
• Support code action fix all commands
• Code action ignore rule quick fixes
• Add optional rule documentation links

[tusbar]

Wouldn't be a bad thing to request migrating this repo to the XO (https://github.com/xojs) organization.

[spence-s]

@tusbar I'd like to do that, however, I am only a collaborator on a user repository here - so I don't believe there is anything I can do. @SamVerschueren Would you be ok to work with @sindresorhus to move this to the xo org? - It would be nice to have a few more permissions that I don't think I can get as a collaborator on a user repo. For instance, I'd like to make issue templates to suggest common debugging steps and currently don't believe I can do.

[SamVerschueren]

I'm ok with moving it. @sindresorhus what do you think?

[sindresorhus]

@SamVerschueren 👍

[yakov116]

@spence-s can you clean up all the issues?

[tusbar]

@spence-s is anything blocking the release process? Can we help in any way? I’d like to start updating xo on my repos and don’t want to ask people to switch to your fork.

[SamVerschueren]

I'm in contact with the VSC team to add @spence-s as contributor but for some reason what they did didn't work. So we're trying to resolve it. Sorry for the inconvenience.

[sindresorhus]

@SamVerschueren I think you should have access to move the repo to the organization. And if not, just move it to me and I'll move it to the organization.

[SamVerschueren]

Oh yes. I'll try to do it this evening. But I think the question was for releasing it in the marketplace.

[spence-s]

The VScode team has resolved publishing issues and I have released the extension updates under the original https://marketplace.visualstudio.com/items?itemName=samverschueren.linter-xo

[spence-s]

Closing this road map as most of the goals have been met now. Will make individual issues for new features going forward.