Follow the Object Rest Destructuring specification

[diegohaz]

https://github.com/sebmarkbage/ecmascript-rest-spread/blob/master/Rest.md

Currently, we are breaking this rule on some component props destructuring:

let { ...x, y, z } = obj; // syntax error

The components are:

• Input
• Link
• Feature
• IconButton
• IconLink
• Modal
• Table

The solution is probably as simple as changing this:

const Feature = ({ icon, title, link, children, ...props, soon }) => {

to this:

const Feature = ({ icon, title, link, children, ...props }) => {
  const { soon } = props

I'll leave this issue here for a while for the case of someone wants to contribute.

[antoinerey]

What does produce ?

const Feature = ({ icon, title, link, children, ...props, soon }) => {

Does it :

1. make soon available as variable
2. but, does not extract soon from props (so props.soon exists) ?

[diegohaz]

make soon available as variable
but, does not extract soon from props (so props.soon exists) ?

Exactly. This is currently possible with Babel, but isn't in the spec, so might break in the future.

[diegohaz]

Maybe just changing references from too to props.too should be more elegant. I don't know, only IconButton has many variables after props.