Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

How to use my own rules when using the "Create eslintrc.json file" command? #264

Closed
mkvlrn-cm42 opened this issue Jul 14, 2017 · 4 comments
Closed

How to use my own rules when using the "Create eslintrc.json file" command? #264

mkvlrn-cm42 opened this issue Jul 14, 2017 · 4 comments
Labels
feature-request Request for new features or functionality info-needed Issue requires more information from poster *out-of-scope Posted issue is not in scope of VS Code

Comments

@mkvlrn-cm42
Copy link

Is there a template somewhere? I couldn't find it in the extension directory.

I just want to paste my own eslintrc file on top of it, as I have a standard one that is used by 99% of my projects.

Thanks.
@dbaeumer dbaeumer added the feature-request Request for new features or functionality label Aug 4, 2017
@dbaeumer dbaeumer added this to the Backlog milestone Aug 4, 2017
@dbaeumer
Copy link
Member

dbaeumer commented Aug 4, 2017

This is currently not supported.

@dbaeumer dbaeumer added the *out-of-scope Posted issue is not in scope of VS Code label Nov 21, 2017
@Hirse
Copy link
Member

Hirse commented May 21, 2018

@mikevaleriano For your use case it might make more sense to publish your configuration and import it as a dependency to your project. That way, they also stay up-to-date.

Slightly related: #423

@dbaeumer dbaeumer added the info-needed Issue requires more information from poster label May 22, 2018
@dbaeumer
Copy link
Member

I agree with @Hirse

OK to close?

@mkvlrn-cm42
Copy link
Author

Yes, I've been doing something similar, but linking that way is faster and more maintainable. Thanks.

@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 6, 2018
@dbaeumer dbaeumer removed this from the Backlog milestone Dec 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature-request Request for new features or functionality info-needed Issue requires more information from poster *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dbaeumer @Hirse @mkvlrn-cm42