Why ISN'T `foo: 'bar'` a syntax error in Javascript? [duplicate]

Question

A coworker of mine wrote the ES6 line of code...

return map(orderedContentUuids, contentUuid => { uuid: contentUuid });

As you can probably guess he intended to return the object {uuid: contentUuid }, but since its an arrow function, the curly brace { actually starts a new block. (The correct code would be return map(orderedContentUuids, contentUuid => ({ uuid: contentUuid }));).

But, unexpectedly, this code transpiles and runs without an error. There's no error because uuid: contentUuid seems to evaluate to contentUuid.

You can see then that if you put into your JavaScript console foo: 'bar' it evaluates to "bar".

Huh? What's going on. Since when is that valid JS?

Chris W. · Accepted Answer · 2017-12-21 00:29:15Z

6

Ooops. I just figured it out.

foo: 'bar' is evaluated as a "label", which I did not realize was a JavaScript feature.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/label

answered Dec 21, 2017 at 0:29

Chris W.

39.5k37 gold badges105 silver badges139 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Sébastien Over a year ago

Indeed curly braces would not be considered an object in this context.

Collectives™ on Stack Overflow

Why ISN'T `foo: 'bar'` a syntax error in Javascript? [duplicate]

1 Answer 1

1 Comment

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Linked

Related