SharePoint Customization Analysis Framework (SPCAF)

Consider using a "Value and Type" comparison in if statements

Consider not using 'arguments.callee' and arguments.caller'

Consider to not use empty labels

Missing break in switch statement

__iterator__ is a reserved word

Do not reassign native objects

Do not use new keyword without assignment

Disallow use of the function constructor

Consider to disallow primitive wrapper instances

__proto__ is a reserved word

With statement is not recommended

Consider to not allow assignment in return statements

Always supply a radix with parseInt

Do not declare code in the global namespace directly

Use the latest versions of JavaScript libraries

Argument was defined but not referenced

A function was defined but not referenced

Function has not been declared

A variable was defined but not set or referenced

Function name should be a simple identifier; possible browser-specific implementation

Object constructor takes no arguments

Consider replacing maximum numeric literal with Number.MAX_VALUE

Consider replacing minimum numeric literal with Number.MIN_VALUE

Do not use new keyword without assignment

This creates an object without assignment to a variable

CheckId	SPC058907
TypeName	NoNewKeywordWithoutAssign
Severity	Warning
Type	JavaScriptFile

Bad Practice

new Foo();

Good Practice

var thing = new foo();

// Foo() on its own can also be not considered a warning
Foo();

Disallow new For Side Effects (no-new)

Message Suppression

Copyright © 2009 - 2020 Rencore

SharePoint Customization Analysis Framework (SPCAF), 7.15.0.0

Disclaimer: The views and opinions expressed in this documentation and in SPCAF do not necessarily reflect the opinions and recommendations of Microsoft or any member of Microsoft. SPCAF and RENCORE are registered trademarks of Rencore. All other trademarks, service marks, collective marks, copyrights, registered names, and marks used or cited by this documentation are the property of their respective owners.