mirror of
https://github.com/facebook/react.git
synced 2025-11-01 09:12:30 +00:00
Sebastian Markbåge
18875b2401
* Remove toString of dangerouslySetInnerHTML As far as I can tell, the toString call was added here: https://github.com/facebook/react/commit/caae627cd557812d28d11237b34bff6c661ea8bc#diff-5574f655d491348f422bca600ff6711dR887 It was never really needed. Subsequently when we added Trusted Types, this needed to be changed to a special call but we really should just always let it pass through. * Remove special casing of toString values when enableTrustedTypesIntegration As far as I can tell, we only toString in user space because of IE8/9. We don't really support IE8/9 anymore and by the time this flag is on, we should be able to deprecate it. Unless this is also an issue in IE11. I haven't tested yet.
38 lines
900 B
JavaScript
38 lines
900 B
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.
|
|
*
|
|
* @flow
|
|
*/
|
|
|
|
export opaque type ToStringValue =
|
|
| boolean
|
|
| number
|
|
| Object
|
|
| string
|
|
| null
|
|
| void;
|
|
|
|
// Flow does not allow string concatenation of most non-string types. To work
|
|
// around this limitation, we use an opaque type that can only be obtained by
|
|
// passing the value through getToStringValue first.
|
|
export function toString(value: ToStringValue): string {
|
|
return '' + (value: any);
|
|
}
|
|
|
|
export function getToStringValue(value: mixed): ToStringValue {
|
|
switch (typeof value) {
|
|
case 'boolean':
|
|
case 'number':
|
|
case 'object':
|
|
case 'string':
|
|
case 'undefined':
|
|
return value;
|
|
default:
|
|
// function, symbol are assigned as empty strings
|
|
return '';
|
|
}
|
|
}
|