Bug: MockInstance.scope(); is mentioned in "Getting started" doc although being unnecessary nowadays(?)

[rklec]

Bug: MockInstance.scope(); is mentioned in "Getting started" doc although being unnecessary nowadays(?)

[satanTime]

Yep - each doc page has [Edit this page] link.

Also, please check that the commit message has a correct format: docs: bla bla bla

[satanTime]

Hi @rklec,

that's partially true and ng-mocks used to create and destroy scopes automatically.
However, due to recent changes in jest, it became impossible, and, in case of jest, scopes should be created and destroyed manually.

The guide how to configure automatic scopes for jasmine is here: https://ng-mocks.sudo.eu/extra/install
The issue in jest is here: jestjs/jest#11483.

[rklec]

Okay, but then this should be documented? That it is only needed for jest?

[satanTime]

By default ng-mocks doesn't do that out of shelf, developers should manually add code to src/test.ts.

[satanTime]

Maybe I don't get your idea, could you explain the problem in more details?

Basically by default everybody should use scopes if they want to use MockInstance, and if they want to reduce repetition and they use jasmine, then they can configure test.ts to create scope automatically.

[rklec]

Hmm are the docs on GitHub? I could create a PR?

[satanTime]

v14.12.0 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.