Showing 77 of 77 total issues
Missing standard property 'box-shadow' to go along with '-moz-box-shadow'. Open
-webkit-box-shadow: 0 0 25px #777; -moz-box-shadow: 0 0 25px #777;- Exclude checks
Rule doesn't have all its properties in alphabetical order. Open
ul.sections > li > div.content {- Exclude checks
Element (span.lineno) is overqualified, just use .lineno without element name. Open
span.lineno { background-color: #f0f0f0; padding: 0 5px 0 5px; }- Exclude checks
Rule doesn't have all its properties in alphabetical order. Open
@font-face {- Exclude checks
Rule doesn't have all its properties in alphabetical order. Open
.annotation pre {- Exclude checks
Don't use IDs in selectors. Open
#jump_page .source {- Exclude checks
Unexpected console statement. Open
console.info(`paperboy-communicator stdout: ${stdout}`);- Read upRead up
- Exclude checks
disallow the use of console (no-console)
In JavaScript that is designed to be executed in the browser, it's considered a best practice to avoid using methods on console. Such messages are considered to be for debugging purposes and therefore not suitable to ship to the client. In general, calls using console should be stripped before being pushed to production.
console.log("Made it here.");
console.error("That shouldn't have happened.");Rule Details
This rule disallows calls to methods of the console object.
Examples of incorrect code for this rule:
/*eslint no-console: "error"*/
console.log("Log a debug level message.");
console.warn("Log a warn level message.");
console.error("Log an error level message.");Examples of correct code for this rule:
/*eslint no-console: "error"*/
// custom console
Console.log("Hello world!");Options
This rule has an object option for exceptions:
-
"allow"has an array of strings which are allowed methods of theconsoleobject
Examples of additional correct code for this rule with a sample { "allow": ["warn", "error"] } option:
/*eslint no-console: ["error", { allow: ["warn", "error"] }] */
console.warn("Log a warn level message.");
console.error("Log an error level message.");When Not To Use It
If you're using Node.js, however, console is used to output information to the user and so is not strictly used for debugging purposes. If you are developing for Node.js then you most likely do not want this rule enabled.
Related Rules
- [no-alert](no-alert.md)
- [no-debugger](no-debugger.md) Source: http://eslint.org/docs/rules/
The property -moz-appearance is compatible with -webkit-appearance and should be included as well. Open
-webkit-appearance: button; /* 2 */- Exclude checks
2 IDs in the selector, really? Open
#jump_to:hover #jump_wrapper {- Exclude checks
Unqualified attribute selectors are known to be slow. Open
[hidden] {- Exclude checks
Outlines should only be modified using :focus. Open
a:active,- Exclude checks
Expected (none | button | button-bevel | caps-lock-indicator | caret | checkbox | default-button | listbox | listitem | media-fullscreen-button | media-mute-button | media-play-button | media-seek-back-button | media-seek-forward-button | media-slider | media-sliderthumb | menulist | menulist-button | menulist-text | menulist-textfield | push-button | radio | searchfield | searchfield-cancel-button | searchfield-decoration | searchfield-results-button | searchfield-results-decoration | slider-horizontal | slider-vertical | sliderthumb-horizontal | sliderthumb-vertical | square-button | textarea | textfield | scrollbarbutton-down | scrollbarbutton-left | scrollbarbutton-right | scrollbarbutton-up | scrollbargripper-horizontal | scrollbargripper-vertical | scrollbarthumb-horizontal | scrollbarthumb-vertical | scrollbartrack-horizontal | scrollbartrack-vertical) but found 'textfield'. Open
-webkit-appearance: textfield; /* 1 */- Exclude checks
Unexpected console statement. Open
console.error(`Could not start redis on ${address}:${port}`);- Read upRead up
- Exclude checks
disallow the use of console (no-console)
In JavaScript that is designed to be executed in the browser, it's considered a best practice to avoid using methods on console. Such messages are considered to be for debugging purposes and therefore not suitable to ship to the client. In general, calls using console should be stripped before being pushed to production.
console.log("Made it here.");
console.error("That shouldn't have happened.");Rule Details
This rule disallows calls to methods of the console object.
Examples of incorrect code for this rule:
/*eslint no-console: "error"*/
console.log("Log a debug level message.");
console.warn("Log a warn level message.");
console.error("Log an error level message.");Examples of correct code for this rule:
/*eslint no-console: "error"*/
// custom console
Console.log("Hello world!");Options
This rule has an object option for exceptions:
-
"allow"has an array of strings which are allowed methods of theconsoleobject
Examples of additional correct code for this rule with a sample { "allow": ["warn", "error"] } option:
/*eslint no-console: ["error", { allow: ["warn", "error"] }] */
console.warn("Log a warn level message.");
console.error("Log an error level message.");When Not To Use It
If you're using Node.js, however, console is used to output information to the user and so is not strictly used for debugging purposes. If you are developing for Node.js then you most likely do not want this rule enabled.
Related Rules
- [no-alert](no-alert.md)
- [no-debugger](no-debugger.md) Source: http://eslint.org/docs/rules/
Don't use IDs in selectors. Open
#jump_to a {- Exclude checks
Don't use IDs in selectors. Open
#background {- Exclude checks
Rule doesn't have all its properties in alphabetical order. Open
ul.sections > li > div.annotation {- Exclude checks
Rule doesn't have all its properties in alphabetical order. Open
pre code {- Exclude checks