Object.create always returns {}

[pandazy]

No matter what is passed into Object.create as its first parameter, it just returns {}, I am not sure if this is designed in purpose, if yes, I wonder if there is a reason and if there is a workaround. Here is a simple example of test case for this

describe('object.create', function(){
   it('should return return Object.create result', function(){
      console.log('\n','result of Object.create() ===>', Object.create({ a:1, b:2}));
   });
});

The running result of the code above may look like this:

Using Jest CLI v0.8.2, jasmine1
Running 1 test suite...
result of Object.create() ===> {}
PASS  __tests__/simple.js (0.264s)
1 test passed (1 total in 1 test suite, run time 0.658s)

Obviously I am expecting it to return { a: 1, b: 2} instead of {}
I would like to appreciate your effort for examining this issue.

[cpojer]

can you console.log(Object.create)? Are you overwriting it with your own implementation that is being mocked?

(I'm closing this because it is likely not an issue with jest and more like a question, but happy to reopen if it turns out to be one :) )

[Sebmaster]

This is a peculiarity of console.log, but it works correctly. Object.create attaches the object you provide as the prototype. And console.log doesn't log the prototype, only the own_properties of the object.

See:

> Object.create({a:1})
{}
> Object.create({a:1}).a
1
> x = Object.create({a:1})
{}
> x.b = 2
2
> x
{ b: 2 }
> x.a
1

[cpojer]

@Sebmaster thanks for the explanation! I don't normally pass anything other than null to Object.create.

[pandazy]

Yes, I confirmed, great thanks for your answer.

On Thu, Jan 28, 2016 at 11:21 AM, Sebastian Mayr notifications@github.com
wrote:

This is a peculiarity of console.log, but it works correctly.
Object.create attaches the object you provide as the prototype. And
console.log doesn't log the prototype, only the own_properties of the
object.

See:

Object.create({a:1})
{}
Object.create({a:1}).a
1
x = Object.create({a:1})
{}
x.b = 2
2
x
{ b: 2 }

—
Reply to this email directly or view it on GitHub
#695 (comment).

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.