Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

fix(eslint-plugin): [no-misused-spread] correct and elaborate string spread report message#10751

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

JoshuaKGoldberg
Copy link
Member

PR Checklist

Overview

Updates the report message for a string spread to bemoanboth... and.split("").

💖

@typescript-eslint
Copy link
Contributor

Thanks for the PR,@JoshuaKGoldberg!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently onhttps://opencollective.com/typescript-eslint.

@netlifyNetlify
Copy link

netlifybot commentedJan 31, 2025
edited
Loading

Deploy Preview fortypescript-eslint ready!

NameLink
🔨 Latest commit1af6d6f
🔍 Latest deploy loghttps://app.netlify.com/sites/typescript-eslint/deploys/67a3f59ff07f3d00088de281
😎 Deploy Previewhttps://deploy-preview-10751--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 98 (🔴 down 1 from production)
Accessibility: 100 (no change from production)
Best Practices: 92 (no change from production)
SEO: 98 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to yourNetlify site configuration.

@nx-cloudNx Cloud
Copy link

nx-cloudbot commentedJan 31, 2025
edited
Loading

View yourCI Pipeline Execution ↗ for commit1af6d6f.

CommandStatusDurationResult
nx run-many --target=build --exclude website --...✅ Succeeded4sView ↗
nx run-many --target=clean✅ Succeeded11sView ↗

☁️Nx Cloud last updated this comment at2025-02-05 23:50:13 UTC

'- .split("") produces UTF-16 code units, which breaks rich characters in many languages',
"If this string does not need to preserve emojis or other non-English characters, disable this lint rule on this line or configure the 'allow' rule option.",
'Otherwise, consider using `Intl.Segmenter`.',
].join('\n'),
Copy link
MemberAuthor

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

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 usingIntl.Segmenter
  • Otherwise, if this string does not need to preserve emojis ...

kirkwaiblinger reacted with thumbs up emoji

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

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
Co-authored-by: Kirk Waiblinger <53019676+kirkwaiblinger@users.noreply.github.com>
Copy link
Member

@kirkwaiblingerkirkwaiblinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

The PR has not been updated with the people's demands 😜https://github.com/typescript-eslint/typescript-eslint/pull/10751/files#r1942930884

Wondering if you forgot to push?

ArnaudBarre and JoshuaKGoldberg reacted with laugh emoji
@JoshuaKGoldberg
Copy link
MemberAuthor

🤦

kirkwaiblinger reacted with laugh emoji

kirkwaiblinger
kirkwaiblinger previously approved these changesFeb 5, 2025
@codecovCodecov
Copy link

codecovbot commentedFeb 5, 2025
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.28%. Comparing base(3372a4a) to head(1af6d6f).
Report is 26 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@##             main   #10751      +/-   ##==========================================+ Coverage   87.26%   87.28%   +0.01%==========================================  Files         450      450                Lines       15715    15739      +24       Branches     4601     4609       +8     ==========================================+ Hits        13714    13737      +23  Misses       1645     1645- Partials      356      357       +1
FlagCoverage Δ
unittest87.28% <ø> (+0.01%)⬆️

Flags with carried forward coverage won't be shown.Click here to find out more.

Files with missing linesCoverage Δ
...kages/eslint-plugin/src/rules/no-misused-spread.ts100.00% <ø> (ø)

... and9 files with indirect coverage changes

Copy link
Contributor

@ArnaudBarreArnaudBarre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

🚀

@kirkwaiblingerkirkwaiblinger added the 1 approval>=1 team member has approved this PR; we're now leaving it open for more reviews before we merge labelFeb 10, 2025
@JoshuaKGoldberg
Copy link
MemberAuthor

I'd normally prefer to leave this open for a couple more days to get a full week (https://typescript-eslint.io/maintenance/pull-requests#approvals). But this is kind of a hot topic. Merging a couple days early.

@JoshuaKGoldbergJoshuaKGoldberg merged commit7acfb5f intotypescript-eslint:mainFeb 10, 2025
62 of 63 checks passed
@JoshuaKGoldbergJoshuaKGoldberg deleted the no-misused-spread-string-report branchFebruary 10, 2025 16:40
renovatebot added a commit to andrei-picus-tink/auto-renovate that referenced this pull requestFeb 11, 2025
| datasource | package                          | from   | to     || ---------- | -------------------------------- | ------ | ------ || npm        | @typescript-eslint/eslint-plugin | 8.23.0 | 8.24.0 || npm        | @typescript-eslint/parser        | 8.23.0 | 8.24.0 |## [v8.24.0](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#8240-2025-02-10)##### 🚀 Features-   **eslint-plugin:** \[no-unnecessary-condition] make `allowConstantLoopConditions` more granular ([#10639](typescript-eslint/typescript-eslint#10639))##### 🩹 Fixes-   **eslint-plugin:** \[no-misused-spread] correct and elaborate string spread report message ([#10751](typescript-eslint/typescript-eslint#10751))-   **eslint-plugin:** \[restrict-plus-operands] report adding bigints to strings when `allowNumberAndString` is `false` ([#10737](typescript-eslint/typescript-eslint#10737))##### ❤️ Thank You-   Josh Goldberg ✨-   noah-   Ronen AmielYou can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
renovatebot added a commit to andrei-picus-tink/auto-renovate that referenced this pull requestFeb 11, 2025
| datasource | package                          | from   | to     || ---------- | -------------------------------- | ------ | ------ || npm        | @typescript-eslint/eslint-plugin | 8.23.0 | 8.24.0 || npm        | @typescript-eslint/parser        | 8.23.0 | 8.24.0 |## [v8.24.0](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#8240-2025-02-10)##### 🚀 Features-   **eslint-plugin:** \[no-unnecessary-condition] make `allowConstantLoopConditions` more granular ([#10639](typescript-eslint/typescript-eslint#10639))##### 🩹 Fixes-   **eslint-plugin:** \[no-misused-spread] correct and elaborate string spread report message ([#10751](typescript-eslint/typescript-eslint#10751))-   **eslint-plugin:** \[restrict-plus-operands] report adding bigints to strings when `allowNumberAndString` is `false` ([#10737](typescript-eslint/typescript-eslint#10737))##### ❤️ Thank You-   Josh Goldberg ✨-   noah-   Ronen AmielYou can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
@github-actionsgithub-actionsbot locked asresolvedand limited conversation to collaboratorsFeb 18, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@ArnaudBarreArnaudBarreArnaudBarre left review comments

@kirkwaiblingerkirkwaiblingerkirkwaiblinger approved these changes

Assignees
No one assigned
Labels
1 approval>=1 team member has approved this PR; we're now leaving it open for more reviews before we merge
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Bug: [no-misused-spread] report for string spread harmfully conflates Unicode code points with UTF-16 code units
3 participants
@JoshuaKGoldberg@ArnaudBarre@kirkwaiblinger

[8]ページ先頭

©2009-2025 Movatter.jp