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

express.js is not using standard #957

Closed
miguelmota opened this issue Jul 21, 2017 · 4 comments

Comments

@miguelmota
Copy link

commented Jul 21, 2017

standard not in package.json

random snippet from source code

function View(name, options) {
  var opts = options || {};

  this.defaultEngine = opts.defaultEngine;
  this.ext = extname(name);
  this.name = name;
  //...
}

suggest removing from README

@dougwilson

This comment has been minimized.

Copy link

commented Jul 21, 2017

There are other random snippets from the source that are standard, since the contribution guidelines in Express.js state that all new and changed code must be StandardJS.

@dougwilson

This comment has been minimized.

Copy link

commented Jul 21, 2017

I'm not dure how the logo got there, but at leadt policy wise express requires standardjs style. Almost all of our code base has been updayed so far, including all the following:

https://github.com/expressjs/body-parser
https://github.com/expressjs/compression
https://github.com/expressjs/cookie-parser
https://github.com/expressjs/cookie-session
https://github.com/expressjs/csurf
https://github.com/expressjs/errorhandler
https://github.com/expressjs/generator
https://github.com/expressjs/method-override
https://github.com/expressjs/morgan
https://github.com/expressjs/multer
https://github.com/expressjs/response-time
https://github.com/expressjs/serve-favicon
https://github.com/expressjs/serve-static
https://github.com/expressjs/timeout
https://github.com/expressjs/vhost

Ones that have only been converted partially are ones which used a semicolon style and have many open pull requests, since removing the semicolons across the board will prevent the pull requests from merging.

If you have tips on how to convert a codebase without redoing all outstanding pull requests, please let us know! It can even be a good first contribution to provide an implementation on how to do a rolling change.

@miguelmota

This comment has been minimized.

Copy link
Author

commented Jul 22, 2017

ooh gotcha, thanks

@miguelmota miguelmota closed this Jul 22, 2017

@bcomnes

This comment has been minimized.

Copy link
Member

commented Jul 22, 2017

As long as it's standard in spirit 😜

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
3 participants
You can’t perform that action at this time.