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

More configuration information #1054

Closed
Zyst opened this issue Mar 20, 2017 · 1 comment
Closed

More configuration information #1054

Zyst opened this issue Mar 20, 2017 · 1 comment
Labels
locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting.

Comments

@Zyst
Copy link
Contributor

Zyst commented Mar 20, 2017

Heya guys, awesome tool! I'm having a bit of a problem in the sense that I haven't the slightest clue as to how to configure it, though.

Like, say I have a new project, how do I make prettier actions (I'm running through vim) grab their settings from some file?

Is there a way to plug it to use the same settings as ESLint? I saw there's quite a few extensions, including eslint-plugin-prettier which lets prettier throw errors through eslint, but that's not really what I want.

To finally get around to making my point: I would love to see README extended to cover these questions to some degree.

Is it like Babel and Eslint where if there's no local file it can go to root (~) and look for a file there with 'sane' default basics?

I'm really sorry if this has been answered before It totally (Sort of) has been, from what I've seen in:

#644 #98 #154 and #40, there's even work arounds there, so most of the problems I had above are "solved". I still would still love you guys forever if some of these questions could be answered in the README, it was quite a wild goose chase.

@vjeux
Copy link
Contributor

vjeux commented Mar 21, 2017

Thanks for the issue! You can see here the proposal for configuration: #918

The idea is to put project configuration in package.json and for prettier to read it. We haven't had the time to actually implement it yet. I'm going to close this issue. If you can chime in the proposal if you have any suggestions that would be awesome!

@vjeux vjeux closed this as completed Mar 21, 2017
@lock lock bot added the locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. label Jul 8, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 8, 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.
Projects
None yet
Development

No branches or pull requests

2 participants