requiring json - odd behaviour

[gnesher]

I've just started using Jest and was requiring a JSON file with fake data to use in the tests and encountered the following behaviour:

If I don't use jest.dontMock the JSON file is imported, but boolean variables get removed.

Mind you, I should have used jest.dontMock to begin with.
Having said that I'm not sure why Jest would return all the properties except the boolean ones.

[dangerbell]

I just noticed this as well. Very confusing.

Here's a sample file and a jest test to show the behaviour:

SimpleObject.js:

module.exports = {
  "boolean": true,
  "stringly": "string",
  "numberly": 23
}

__ tests __/test.js

describe('Boolean Property Test', function() {
  it('should mock boolean object properties', function() {
    expect(require("../SimpleObject")).toEqual({
      "boolean": true,
      "stringly": "string",
      "numberly": 23
    });
  });
});

[arnihermann]

I've noticed this as well.

[isay-sosa]

I'm having the same issue with arrays

// user.json
{
  "user": {
    "id": 3,
    "comments": [
      {
        "id": 1,
        "body": "My Comment"
      }
    ]
  }
}

After requiring it:

// require('user.json')
{
  "user": {
    "id": 3,
    "comments": []
  }
}

[cmmcleod]

I had the same issue when importing JSON fixtures. However requireActual seems to do the trick:

var data = require.requireActual('./fixtures/some_data');

[cpojer]

This will be fixed by #713 in 0.9.0 so I'm closing this issue out.

[mgenev]

Mocking arrays is also broken, they come out empty with jest

[cpojer]

No it is not. Mocking an array will give you an empty array. If that is not what you expect, you can explicitly define it or unmock it.

[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.