feat(linter): add oxc/no-rest-spread-properties rule

[mysteryven]

People open this rule may have some specific purpose, I am deliberating about whether to add a custom message.

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

[mysteryven]

• feat(linter): add oxc/no-rest-spread-properties rule #3432 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @mysteryven and the rest of your teammates on Graphite

[codspeed-hq]

CodSpeed Performance Report

Merging #3432 will not alter performance

_{Comparing 05-27-feat_linter_add_oxc/no-rest-spread-properties_rule (250d26d) with main (0d2c977)}

Summary

✅ 22 untouched benchmarks

[Boshen]

What's the difference between this and https://github.com/mysticatea/eslint-plugin-es/blob/v1.4.1/docs/rules/no-spread-elements.md

We need to be careful!

• es2018 https://github.com/mysticatea/eslint-plugin-es/blob/v1.4.1/docs/rules/no-rest-spread-properties.md
• es2015 - https://github.com/mysticatea/eslint-plugin-es/blob/v1.4.1/docs/rules/no-spread-elements.md

As for error message, I think we should accept an error message, because we don't know what the intent is.

[mysteryven]

What's the difference between this and mysticatea/eslint-plugin-es@v1.4.1/docs/rules/no-spread-elements.md

We will only ban object spread/rest properties, this aligns "ObjectExpression > SpreadElement" and "ObjectExpression > SpreadElement" in Vue's config file for no-restricted-syntax

I think we should accept an error message

Done.

[graphite-app]

Merge activity

• May 28, 11:03 AM EDT: The merge label 'merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.