mirror of
https://github.com/nodejs/node.git
synced 2025-05-06 06:38:13 +00:00

There has been occasional nits for spacing in object literals in PRs but the project does not lint for it and it is not always handled consistently in the existing code, even on adjacent lines of a file. This change enables a linting rule requiring no space between the key and the colon, and requiring at least one space (but allowing for more so property values can be lined up if desired) between the colon and the value. This appears to be the most common style used in the current code base. Example code the complies with lint rule: myObj = { foo: 'bar' }; Examples that do not comply with the lint rule: myObj = { foo : 'bar' }; myObj = { foo:'bar' }; PR-URL: https://github.com/nodejs/node/pull/6592 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
29 lines
883 B
JavaScript
29 lines
883 B
JavaScript
'use strict';
|
|
|
|
const common = require('../common');
|
|
const http = require('http');
|
|
const net = require('net');
|
|
const assert = require('assert');
|
|
|
|
const reqstr = 'HTTP/1.1 200 OK\r\n' +
|
|
'Content-Length: 1\r\n' +
|
|
'Transfer-Encoding: chunked\r\n\r\n';
|
|
|
|
const server = net.createServer((socket) => {
|
|
socket.write(reqstr);
|
|
});
|
|
|
|
server.listen(common.PORT, () => {
|
|
// The callback should not be called because the server is sending
|
|
// both a Content-Length header and a Transfer-Encoding: chunked
|
|
// header, which is a violation of the HTTP spec.
|
|
const req = http.get({port: common.PORT}, (res) => {
|
|
assert.fail(null, null, 'callback should not be called');
|
|
});
|
|
req.on('error', common.mustCall((err) => {
|
|
assert(/^Parse Error/.test(err.message));
|
|
assert.equal(err.code, 'HPE_UNEXPECTED_CONTENT_LENGTH');
|
|
server.close();
|
|
}));
|
|
});
|