Skip to content

Also export editor converter Node APIs #822

Open
@JoshuaKGoldberg

Description

@JoshuaKGoldberg

🚀 Feature Request

Following #732 to add a Node API and #820 to add a standalone comment conversion API, it might also be useful for Node API consumers to be able to convert their editor configuration file(s) automatically.

Existing Behavior

The convertEditorConfig(s) methods are not exported as a standalone function via the Node API.

Change Proposal

Export standalone equivalent(s) to those methods so that someone could call them to convert their editor configuration(s) without tslint-to-eslint-config using its own file I/O.


@JamesHenry, do you predict wanting to use this as part of the angular-eslint schematic (angular-eslint/angular-eslint#173)? If so, I can tackle this pretty quickly alongside #820. If not, this would be a good contribution opportunity for someone new to tackle if they're interested. This isn't necessary for the angular-eslint schematics. Which makes it a perfect good first issue for someone who'd like to try adding to tslint-to-eslint-config without time pressure! ✨

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: node APIUsing tslint-to-eslint-config as an npm dependencygood first issueGood for newcomers; welcome aboard!status: accepting prsPlease, send in a PR to resolve this! ✨type: enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions