Feb 10, 2025 · Jan 31, 2025 · Feb 5, 2025 · Feb 5, 2025 · Feb 5, 2025 · Jan 31, 2025
diff --git a/packages/eslint-plugin/src/rules/no-misused-spread.ts b/packages/eslint-plugin/src/rules/no-misused-spread.ts
        'Using the spread operator on a Map in an object will result in an empty object. Did you mean to use `Object.fromEntries(map)` instead?',
      noPromiseSpreadInObject:
        'Using the spread operator on Promise in an object can cause unexpected behavior. Did you forget to await the promise?',
      noStringSpread:
        "Using the spread operator on a string can cause unexpected behavior. Prefer `.split('')` instead.",
      noStringSpread: [
        'Using the spread operator on a string can mishandle special characters, as can `.split("")`.',
        '- `...` produces Unicode code points, which will decompose complex emojis into individual emojis',
        '- .split("") produces UTF-16 code units, which breaks rich characters in many languages',
        'Consider using `Intl.Segmenter` for locale-aware string decomposition.',
        "Otherwise, if you don't need to preserve emojis or other non-Ascii characters, disable this lint rule on this line or configure the 'allow' rule option.",
      ].join('\n'),
    },
    schema: [
      {
diff --git a/packages/eslint-plugin/tests/docs-eslint-output-snapshots/no-misused-spread.shot b/packages/eslint-plugin/tests/docs-eslint-output-snapshots/no-misused-spread.shot
Original file line number	Diff line number	Diff line change
Expand Up		@@ -57,8 +57,13 @@ export default createRule<Options, MessageIds>({
		'Using the spread operator on a Map in an object will result in an empty object. Did you mean to use `Object.fromEntries(map)` instead?',
		noPromiseSpreadInObject:
		'Using the spread operator on Promise in an object can cause unexpected behavior. Did you forget to await the promise?',
		noStringSpread:
		"Using the spread operator on a string can cause unexpected behavior. Prefer `.split('')` instead.",
		noStringSpread: [
		'Using the spread operator on a string can mishandle special characters, as can `.split("")`.',
		'- `...` produces Unicode code points, which will decompose complex emojis into individual emojis',
		'- .split("") produces UTF-16 code units, which breaks rich characters in many languages',
		'Consider using `Intl.Segmenter` for locale-aware string decomposition.',
		"Otherwise, if you don't need to preserve emojis or other non-Ascii characters, disable this lint rule on this line or configure the 'allow' rule option.",
		].join('\n'),
Copy link MemberAuthor JoshuaKGoldbergJan 31, 2025 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. To anybody with opinions on string splitting: please bikeshed theheck out of this message! Copy link Contributor ArnaudBarreFeb 3, 2025 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. Nice! I would prefer having the disable comment sentence as the otherwise with something like If you want to split on graphemes, consider using`Intl.Segmenter` Otherwise, if this string does not need to preserve emojis ... kirkwaiblinger reacted with thumbs up emoji Copy link Member kirkwaiblingerFeb 5, 2025 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. +1. I think it makes sense to say "consider using Intl.Segmenter for robust, locale-aware string decomposition." first, and then "Otherwise, if you don't need to preserve emojis or other non-Ascii characters, disable, etc..." ArnaudBarre reacted with thumbs up emoji Copy link MemberAuthor JoshuaKGoldbergFeb 5, 2025 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. the people have spoken kirkwaiblinger reacted with laugh emoji
		},
		schema: [
		{
Expand Down