block editor - Why is onChange={ ( content ) => setAttributes( { content } )} now used?

admin管理员组

文章数量:1296894

Looking through older tutorials or code for blocks built in 2018/2019 vs the more current blocks, I see two different ways attribute values are set.

For example, the "old" way for an attribute called "content" might be:

onChange={ (newContent) => setAttributes({ content: newContent })}

Whereas in a more modern block:

onChange={ ( content ) => setAttributes( { content } )}

I get it's a minor change but I'm curious if anyone here knows why.

Thanks!

Looking through older tutorials or code for blocks built in 2018/2019 vs the more current blocks, I see two different ways attribute values are set.

For example, the "old" way for an attribute called "content" might be:

onChange={ (newContent) => setAttributes({ content: newContent })}

Whereas in a more modern block:

onChange={ ( content ) => setAttributes( { content } )}

I get it's a minor change but I'm curious if anyone here knows why.

Thanks!

• block-editor

Share Improve this question asked Mar 30, 2021 at 19:28 llysa llysa 16311 silver badge55 bronze badges 0

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 5

Because { content } is shorthand for { content: content } it's a JS thing not a WordPress thing.

Both methods work and do the same thing, but the { content } syntax is shorter, so the variable was named content in newer examples to allow it.

Otherwise, there are no security or performance improvements, it's just a shorter syntax for the same thing.

本文标签： block editorWhy is onChange ( content ) gt setAttributes(content) now used