Skip to content
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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

Docs: Add note about support for object spread (fixes #11136) #11395

Merged
merged 1 commit into from Feb 15, 2019
Merged

Docs: Add note about support for object spread (fixes #11136) #11395

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/rules/prefer-object-spread.md
View file
Open in desktop
Expand Up @@ -2,7 +2,7 @@

When Object.assign is called using an object literal as the first argument, this rule requires using the object spread syntax instead. This rule also warns on cases where an `Object.assign` call is made using a single argument that is an object literal, in this case, the `Object.assign` call is not needed.

Object spread is a declarative alternative which may perform better than the more dynamic, imperative `Object.assign`.
Introduced in ES2018, object spread is a declarative alternative which may perform better than the more dynamic, imperative `Object.assign`.

## Rule Details

Expand Down Expand Up @@ -46,4 +46,4 @@ Object.assign(foo, { ...baz });

## When Not To Use It

When object spread is not available in your codebase.
This rule should not be used unless ES2018 is supported in your codebase.