Skip to content
This repository was archived by the owner on May 6, 2018. It is now read-only.
This repository was archived by the owner on May 6, 2018. It is now read-only.

Configuration file path #32

@inad9300

Description

@inad9300

I see this problem in many extensions... I think it would be more sensitive to include the possibility of defining the path for your own configuration file, instead of trying to guess it. At least specify where should we place it, please, because this "somewhere" you mention doesn't work for any place (the extension says "Unable to find a JSCS configuration file." – I just have a folder where all the code style definitions are stored, including a .jscsrc file).

In general, I think it should be a more direct mapping between the original command-line tool and the editor's extension. Otherwise, the advantages the extension gives are lost because of the lack of flexibility, as I see it.

Thanks.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions