-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Integrate consistent code formatting #1073
Comments
@ptomasroos |
I know that. Will fix a pr in the weekend!
…On 24 Mar 2017 5:22 PM, "Matt Kendall" ***@***.***> wrote:
@ptomasroos <https://github.com/ptomasroos>
Thanks for the suggestion. We do need this. I would be happy to review a
PR for integrating to the project. One style convention we have is to
prefer single quotes, and looks like the default is double quote. I'm not
sure how to configure that on a project level though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1073 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABA-Y7Ae2SigSAamQnP3YH7_0yKxtoOcks5ro-2rgaJpZM4Mn5Iz>
.
|
awesome! |
An alternative could be to use https://standardjs.com/ as well. Might yield smaller amount of changes |
Seems like it might be worth a shot. |
Do you want me to give it a try with standardjs @mkendall07 ? |
Closing with #1111 merged |
Type of issue
Improvement
Description
Prebid.js is a collaboration between multiple companies, many commits / PR are handling reintendations, formatting fixes ect. Instead of spending time of this we could do as many open source projects are these days, move on to a consistent formatting tool. My suggestion would be prettier which is sponsored by Facebook and getting a lot of attention these days. https://github.com/prettier/prettier
We use it internally and have a git prehook which causes people to run formatting either on save with files or via a npm run command to make sure that PR's that are entered is consistently formatted.
I'm happy to provide a PR if we consider this to be a good idea.
The text was updated successfully, but these errors were encountered: