mirror of
https://github.com/zebrajr/react.git
synced 2025-12-06 12:20:20 +01:00
* Revise ESLint rules for string coercion
Currently, react uses `'' + value` to coerce mixed values to strings.
This code will throw for Temporal objects or symbols.
To make string-coercion safer and to improve user-facing error messages,
This commit adds a new ESLint rule called `safe-string-coercion`.
This rule has two modes: a production mode and a non-production mode.
* If the `isProductionUserAppCode` option is true, then `'' + value`
coercions are allowed (because they're faster, although they may
throw) and `String(value)` coercions are disallowed. Exception:
when building error messages or running DEV-only code in prod
files, `String()` should be used because it won't throw.
* If the `isProductionUserAppCode` option is false, then `'' + value`
coercions are disallowed (because they may throw, and in non-prod
code it's not worth the risk) and `String(value)` are allowed.
Production mode is used for all files which will be bundled with
developers' userland apps. Non-prod mode is used for all other React
code: tests, DEV blocks, devtools extension, etc.
In production mode, in addiiton to flagging `String(value)` calls,
the rule will also flag `'' + value` or `value + ''` coercions that may
throw. The rule is smart enough to silence itself in the following
"will never throw" cases:
* When the coercion is wrapped in a `typeof` test that restricts to safe
(non-symbol, non-object) types. Example:
if (typeof value === 'string' || typeof value === 'number') {
thisWontReport('' + value);
}
* When what's being coerced is a unary function result, because unary
functions never return an object or a symbol.
* When the coerced value is a commonly-used numeric identifier:
`i`, `idx`, or `lineNumber`.
* When the statement immeidately before the coercion is a DEV-only
call to a function from shared/CheckStringCoercion.js. This call is a
no-op in production, but in DEV it will show a console error
explaining the problem, then will throw right after a long explanatory
code comment so that debugger users will have an idea what's going on.
The check function call must be in the following format:
if (__DEV__) {
checkXxxxxStringCoercion(value);
};
Manually disabling the rule is usually not necessary because almost all
prod use of the `'' + value` pattern falls into one of the categories
above. But in the rare cases where the rule isn't smart enough to detect
safe usage (e.g. when a coercion is inside a nested ternary operator),
manually disabling the rule will be needed.
The rule should also be manually disabled in prod error handling code
where `String(value)` should be used for coercions, because it'd be
bad to throw while building an error message or stack trace!
The prod and non-prod modes have differentiated error messages to
explain how to do a proper coercion in that mode.
If a production check call is needed but is missing or incorrect
(e.g. not in a DEV block or not immediately before the coercion), then
a context-sensitive error message will be reported so that developers
can figure out what's wrong and how to fix the problem.
Because string coercions are now handled by the `safe-string-coercion`
rule, the `no-primitive-constructor` rule no longer flags `String()`
usage. It still flags `new String(value)` because that usage is almost
always a bug.
* Add DEV-only string coercion check functions
This commit adds DEV-only functions to check whether coercing
values to strings using the `'' + value` pattern will throw. If it will
throw, these functions will:
1. Display a console error with a friendly error message describing
the problem and the developer can fix it.
2. Perform the coercion, which will throw. Right before the line where
the throwing happens, there's a long code comment that will help
debugger users (or others looking at the exception call stack) figure
out what happened and how to fix the problem.
One of these check functions should be called before all string coercion
of user-provided values, except when the the coercion is guaranteed not
to throw, e.g.
* if inside a typeof check like `if (typeof value === 'string')`
* if coercing the result of a unary function like `+value` or `value++`
* if coercing a variable named in a whitelist of numeric identifiers:
`i`, `idx`, or `lineNumber`.
The new `safe-string-coercion` internal ESLint rule enforces that
these check functions are called when they are required.
Only use these check functions in production code that will be bundled
with user apps. For non-prod code (and for production error-handling
code), use `String(value)` instead which may be a little slower but will
never throw.
* Add failing tests for string coercion
Added failing tests to verify:
* That input, select, and textarea elements with value and defaultValue
set to Temporal-like objects which will throw when coerced to string
using the `'' + value` pattern.
* That text elements will throw for Temporal-like objects
* That dangerouslySetInnerHTML will *not* throw for Temporal-like
objects because this value is not cast to a string before passing to
the DOM.
* That keys that are Temporal-like objects will throw
All tests above validate the friendly error messages thrown.
* Use `String(value)` for coercion in non-prod files
This commit switches non-production code from `'' + value` (which
throws for Temporal objects and symbols) to instead use `String(value)`
which won't throw for these or other future plus-phobic types.
"Non-produciton code" includes anything not bundled into user apps:
* Tests and test utilities. Note that I didn't change legacy React
test fixtures because I assumed it was good for those files to
act just like old React, including coercion behavior.
* Build scripts
* Dev tools package - In addition to switching to `String`, I also
removed special-case code for coercing symbols which is now
unnecessary.
* Add DEV-only string coercion checks to prod files
This commit adds DEV-only function calls to to check if string coercion
using `'' + value` will throw, which it will if the value is a Temporal
object or a symbol because those types can't be added with `+`.
If it will throw, then in DEV these checks will show a console error
to help the user undertsand what went wrong and how to fix the
problem. After emitting the console error, the check functions will
retry the coercion which will throw with a call stack that's easy (or
at least easier!) to troubleshoot because the exception happens right
after a long comment explaining the issue. So whether the user is in
a debugger, looking at the browser console, or viewing the in-browser
DEV call stack, it should be easy to understand and fix the problem.
In most cases, the safe-string-coercion ESLint rule is smart enough to
detect when a coercion is safe. But in rare cases (e.g. when a coercion
is inside a ternary) this rule will have to be manually disabled.
This commit also switches error-handling code to use `String(value)`
for coercion, because it's bad to crash when you're trying to build
an error message or a call stack! Because `String()` is usually
disallowed by the `safe-string-coercion` ESLint rule in production
code, the rule must be disabled when `String()` is used.
345 lines
11 KiB
JavaScript
345 lines
11 KiB
JavaScript
/**
|
|
* Copyright (c) Facebook, Inc. and its affiliates.
|
|
*
|
|
* This source code is licensed under the MIT license found in the
|
|
* LICENSE file in the root directory of this source tree.
|
|
*
|
|
* @emails react-core
|
|
*/
|
|
|
|
'use strict';
|
|
|
|
function isEmptyLiteral(node) {
|
|
return (
|
|
node.type === 'Literal' &&
|
|
typeof node.value === 'string' &&
|
|
node.value === ''
|
|
);
|
|
}
|
|
|
|
// Symbols and Temporal.* objects will throw when using `'' + value`, but that
|
|
// pattern can be faster than `String(value)` because JS engines can optimize
|
|
// `+` better in some cases. Therefore, in perf-sensitive production codepaths
|
|
// we require using `'' + value` for string coercion. The only exception is prod
|
|
// error handling code, because it's bad to crash while assembling an error
|
|
// message or call stack! Also, error-handling code isn't usually perf-critical.
|
|
//
|
|
// Non-production codepaths (tests, devtools extension, build tools, etc.)
|
|
// should use `String(value)` because it will never crash and the (small) perf
|
|
// difference doesn't matter enough for non-prod use cases.
|
|
//
|
|
// This rule assists enforcing these guidelines:
|
|
// * `'' + value` is flagged with a message to remind developers to add a DEV
|
|
// check from shared/CheckStringCoercion.js to make sure that the user gets a
|
|
// clear error message in DEV is the coercion will throw. These checks are not
|
|
// needed if throwing is not possible, e.g. if the value is already known to
|
|
// be a string or number.
|
|
// * `String(value)` is flagged only if the `isProductionUserAppCode` option
|
|
// is set. Set this option for prod code files, and don't set it for non-prod
|
|
// files.
|
|
|
|
const ignoreKeys = [
|
|
'range',
|
|
'raw',
|
|
'parent',
|
|
'loc',
|
|
'start',
|
|
'end',
|
|
'_babelType',
|
|
'leadingComments',
|
|
'trailingComments',
|
|
];
|
|
function astReplacer(key, value) {
|
|
return ignoreKeys.includes(key) ? undefined : value;
|
|
}
|
|
|
|
/**
|
|
* Simplistic comparison between AST node. Only the following patterns are
|
|
* supported because that's almost all (all?) usage in React:
|
|
* - Identifiers, e.g. `foo`
|
|
* - Member access, e.g. `foo.bar`
|
|
* - Array access with numeric literal, e.g. `foo[0]`
|
|
*/
|
|
function isEquivalentCode(node1, node2) {
|
|
return (
|
|
JSON.stringify(node1, astReplacer) === JSON.stringify(node2, astReplacer)
|
|
);
|
|
}
|
|
|
|
function isDescendant(node, maybeParentNode) {
|
|
let parent = node.parent;
|
|
while (parent) {
|
|
if (!parent) {
|
|
return false;
|
|
}
|
|
if (parent === maybeParentNode) {
|
|
return true;
|
|
}
|
|
parent = parent.parent;
|
|
}
|
|
return false;
|
|
}
|
|
|
|
function isSafeTypeofExpression(originalValueNode, node) {
|
|
if (node.type === 'BinaryExpression') {
|
|
// Example: typeof foo === 'string'
|
|
if (node.operator !== '===') {
|
|
return false;
|
|
}
|
|
const {left, right} = node;
|
|
|
|
// left must be `typeof original`
|
|
if (left.type !== 'UnaryExpression' || left.operator !== 'typeof') {
|
|
return false;
|
|
}
|
|
if (!isEquivalentCode(left.argument, originalValueNode)) {
|
|
return false;
|
|
}
|
|
// right must be a literal value of a safe type
|
|
const safeTypes = ['string', 'number', 'boolean', 'undefined', 'bigint'];
|
|
if (right.type !== 'Literal' || !safeTypes.includes(right.value)) {
|
|
return false;
|
|
}
|
|
return true;
|
|
} else if (node.type === 'LogicalExpression') {
|
|
// Examples:
|
|
// * typeof foo === 'string' && typeof foo === 'number
|
|
// * typeof foo === 'string' && someOtherTest
|
|
if (node.operator === '&&') {
|
|
return (
|
|
isSafeTypeofExpression(originalValueNode, node.left) ||
|
|
isSafeTypeofExpression(originalValueNode, node.right)
|
|
);
|
|
} else if (node.operator === '||') {
|
|
return (
|
|
isSafeTypeofExpression(originalValueNode, node.left) &&
|
|
isSafeTypeofExpression(originalValueNode, node.right)
|
|
);
|
|
}
|
|
}
|
|
return false;
|
|
}
|
|
|
|
/**
|
|
Returns true if the code is inside an `if` block that validates the value
|
|
excludes symbols and objects. Examples:
|
|
* if (typeof value === 'string') { }
|
|
* if (typeof value === 'string' || typeof value === 'number') { }
|
|
* if (typeof value === 'string' || someOtherTest) { }
|
|
|
|
@param - originalValueNode Top-level expression to test. Kept unchanged during
|
|
recursion.
|
|
@param - node Expression to test at current recursion level. Will be undefined
|
|
on non-recursive call.
|
|
*/
|
|
function isInSafeTypeofBlock(originalValueNode, node) {
|
|
if (!node) {
|
|
node = originalValueNode;
|
|
}
|
|
let parent = node.parent;
|
|
while (parent) {
|
|
if (!parent) {
|
|
return false;
|
|
}
|
|
// Normally, if the parent block is inside a type-safe `if` statement,
|
|
// then all child code is also type-safe. But there's a quirky case we
|
|
// need to defend against:
|
|
// if (typeof obj === 'string') { } else if (typeof obj === 'object') {'' + obj}
|
|
// if (typeof obj === 'string') { } else {'' + obj}
|
|
// In that code above, the `if` block is safe, but the `else` block is
|
|
// unsafe and should report. But the AST parent of the `else` clause is the
|
|
// `if` statement. This is the one case where the parent doesn't confer
|
|
// safety onto the child. The code below identifies that case and keeps
|
|
// moving up the tree until we get out of the `else`'s parent `if` block.
|
|
// This ensures that we don't use any of these "parents" (really siblings)
|
|
// to confer safety onto the current node.
|
|
if (
|
|
parent.type === 'IfStatement' &&
|
|
!isDescendant(originalValueNode, parent.alternate)
|
|
) {
|
|
const test = parent.test;
|
|
if (isSafeTypeofExpression(originalValueNode, test)) {
|
|
return true;
|
|
}
|
|
}
|
|
parent = parent.parent;
|
|
}
|
|
}
|
|
|
|
const missingDevCheckMessage =
|
|
'Missing DEV check before this string coercion.' +
|
|
' Check should be in this format:\n' +
|
|
' if (__DEV__) {\n' +
|
|
' checkXxxxxStringCoercion(value);\n' +
|
|
' }';
|
|
|
|
const prevStatementNotDevCheckMessage =
|
|
'The statement before this coercion must be a DEV check in this format:\n' +
|
|
' if (__DEV__) {\n' +
|
|
' checkXxxxxStringCoercion(value);\n' +
|
|
' }';
|
|
|
|
/**
|
|
* Does this node have an "is coercion safe?" DEV check
|
|
* in the same block?
|
|
*/
|
|
function hasCoercionCheck(node) {
|
|
// find the containing statement
|
|
let topOfExpression = node;
|
|
while (!topOfExpression.parent.body) {
|
|
topOfExpression = topOfExpression.parent;
|
|
if (!topOfExpression) {
|
|
return 'Cannot find top of expression.';
|
|
}
|
|
}
|
|
const containingBlock = topOfExpression.parent.body;
|
|
const index = containingBlock.indexOf(topOfExpression);
|
|
if (index <= 0) {
|
|
return missingDevCheckMessage;
|
|
}
|
|
const prev = containingBlock[index - 1];
|
|
|
|
// The previous statement is expected to be like this:
|
|
// if (__DEV__) {
|
|
// checkFormFieldValueStringCoercion(foo);
|
|
// }
|
|
// where `foo` must be equivalent to `node` (which is the
|
|
// mixed value being coerced to a string).
|
|
if (
|
|
prev.type !== 'IfStatement' ||
|
|
prev.test.type !== 'Identifier' ||
|
|
prev.test.name !== '__DEV__'
|
|
) {
|
|
return prevStatementNotDevCheckMessage;
|
|
}
|
|
let maybeCheckNode = prev.consequent;
|
|
if (maybeCheckNode.type === 'BlockStatement') {
|
|
const body = maybeCheckNode.body;
|
|
if (body.length === 0) {
|
|
return prevStatementNotDevCheckMessage;
|
|
}
|
|
if (body.length !== 1) {
|
|
return (
|
|
'Too many statements in DEV block before this coercion.' +
|
|
' Expected only one (the check function call). ' +
|
|
prevStatementNotDevCheckMessage
|
|
);
|
|
}
|
|
maybeCheckNode = body[0];
|
|
}
|
|
|
|
if (maybeCheckNode.type !== 'ExpressionStatement') {
|
|
return (
|
|
'The DEV block before this coercion must only contain an expression. ' +
|
|
prevStatementNotDevCheckMessage
|
|
);
|
|
}
|
|
|
|
const call = maybeCheckNode.expression;
|
|
if (
|
|
call.type !== 'CallExpression' ||
|
|
call.callee.type !== 'Identifier' ||
|
|
!/^check(\w+?)StringCoercion$/.test(call.callee.name) ||
|
|
!call.arguments.length
|
|
) {
|
|
// `maybeCheckNode` should be a call of a function named checkXXXStringCoercion
|
|
return (
|
|
'Missing or invalid check function call before this coercion.' +
|
|
' Expected: call of a function like checkXXXStringCoercion. ' +
|
|
prevStatementNotDevCheckMessage
|
|
);
|
|
}
|
|
|
|
const same = isEquivalentCode(call.arguments[0], node);
|
|
if (!same) {
|
|
return (
|
|
'Value passed to the check function before this coercion' +
|
|
' must match the value being coerced.'
|
|
);
|
|
}
|
|
}
|
|
|
|
function plusEmptyString(context, node) {
|
|
if (
|
|
node.operator === '+' &&
|
|
(isEmptyLiteral(node.left) || isEmptyLiteral(node.right))
|
|
) {
|
|
let valueToTest = isEmptyLiteral(node.left) ? node.right : node.left;
|
|
if (valueToTest.type === 'TypeCastExpression' && valueToTest.expression) {
|
|
valueToTest = valueToTest.expression;
|
|
}
|
|
|
|
if (
|
|
valueToTest.type === 'Identifier' &&
|
|
['i', 'idx', 'lineNumber'].includes(valueToTest.name)
|
|
) {
|
|
// Common non-object variable names are assumed to be safe
|
|
return;
|
|
}
|
|
if (
|
|
valueToTest.type === 'UnaryExpression' ||
|
|
valueToTest.type === 'UpdateExpression'
|
|
) {
|
|
// Any unary expression will return a non-object, non-symbol type.
|
|
return;
|
|
}
|
|
if (isInSafeTypeofBlock(valueToTest)) {
|
|
// The value is inside an if (typeof...) block that ensures it's safe
|
|
return;
|
|
}
|
|
const coercionCheckMessage = hasCoercionCheck(valueToTest);
|
|
if (!coercionCheckMessage) {
|
|
// The previous statement is a correct check function call, so no report.
|
|
return;
|
|
}
|
|
|
|
context.report({
|
|
node,
|
|
message:
|
|
coercionCheckMessage +
|
|
'\n' +
|
|
"Using `'' + value` or `value + ''` is fast to coerce strings, but may throw." +
|
|
' For prod code, add a DEV check from shared/CheckStringCoercion immediately' +
|
|
' before this coercion.' +
|
|
' For non-prod code and prod error handling, use `String(value)` instead.',
|
|
});
|
|
}
|
|
}
|
|
|
|
function coerceWithStringConstructor(context, node) {
|
|
const isProductionUserAppCode =
|
|
context.options[0] && context.options[0].isProductionUserAppCode;
|
|
if (isProductionUserAppCode && node.callee.name === 'String') {
|
|
context.report(
|
|
node,
|
|
"For perf-sensitive coercion, avoid `String(value)`. Instead, use `'' + value`." +
|
|
' Precede it with a DEV check from shared/CheckStringCoercion' +
|
|
' unless Symbol and Temporal.* values are impossible.' +
|
|
' For non-prod code and prod error handling, use `String(value)` and disable this rule.'
|
|
);
|
|
}
|
|
}
|
|
|
|
module.exports = {
|
|
meta: {
|
|
schema: [
|
|
{
|
|
type: 'object',
|
|
properties: {
|
|
isProductionUserAppCode: {
|
|
type: 'boolean',
|
|
default: false,
|
|
},
|
|
},
|
|
additionalProperties: false,
|
|
},
|
|
],
|
|
},
|
|
create(context) {
|
|
return {
|
|
BinaryExpression: node => plusEmptyString(context, node),
|
|
CallExpression: node => coerceWithStringConstructor(context, node),
|
|
};
|
|
},
|
|
};
|