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.

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

Feature Request: .prettierrc #1290

Closed
grgur opened this issue Apr 15, 2017 · 3 comments
Closed

Feature Request: .prettierrc #1290

grgur opened this issue Apr 15, 2017 · 3 comments
Labels
locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. status:needs discussion Issues needing discussion and a decision to be made before action can be taken

Comments

@grgur
Copy link

grgur commented Apr 15, 2017

Would it make sense to keep configuration in some sort of .prettierrc file?

I feel that would be useful for sharing in teams and usage in whatever IDEs people wanna use.

@jsftwww
Copy link

jsftwww commented Apr 15, 2017

On a related note, I need to ignore some directories. Can we also have a .prettierignore file?

@lydell
Copy link
Member

lydell commented Apr 16, 2017

If you need project-specific prettier config and a .prettierignore right now, running prettier inside eslint --fix using eslint-plugin-prettier works really well.

@vjeux vjeux added the status:needs discussion Issues needing discussion and a decision to be made before action can be taken label Apr 16, 2017
@jlongster
Copy link
Member

We are not going to add two more dot files :) I think it's an anti-pattern to rely on dot files and it's crazy when projects have like ~30 of them just to work with the tooling.

The answer is #918 where we can read from a package.json. As for ignoring files, I'm pretty sure glob supports ignoring paths.

This tool is not interested in embracing complex mechanisms for deriving and inheriting configuration. We are focusing on a simple integration path that other tools, if desired, can build on.

@lock lock bot added the locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. label Jul 7, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. status:needs discussion Issues needing discussion and a decision to be made before action can be taken
Projects
None yet
Development

No branches or pull requests

5 participants