Importing logger from componentParser.js cause parser.test.js to fail

[nbriannl]

Is your request related to a problem?

In MarkBind Version: 2.11.0, I have an issue when importing logger from componentParser.js cause parser.test.js to fail.
For example, calling it accordingly as here

markbind/src/lib/markbind/src/parsers/componentParser.js

Line 7 in 8005582

const logger = require('../../../../util/logger');

will cause parser.test.js to fail as shown below.

As @ang-zeyu has pointed out, this occurs for parser.js as well, which is likely the reason logger isn't used in there as well.

The issue is that parser.test.js mocks the whole fs module, which causes the DailyRotateFile constructor to fail automatically in finding the directory.

Describe the solution you'd like

A simple fix would be to only mock the specific functions of fs relavant to parser.test.js

(Describe your proposed solution here.)

Describe alternatives you've considered

(Write your answer here.)

Additional context

(Write your answer here.)

[ang-zeyu]

Occurs for parser.js as well, which is likely the reason logger isn't used in there as well.

Issue is that parser.test.js mocks the whole fs module, which causes the DailyRotateFile constructor to fail automatically in finding the directory.
A simple fix would be to only mock the specific functions of fs relavant to parser.test.js

Perhaps this issue could be renamed as such

Thereafter a new issue could be opened Standardise usage of console.log and logger.log, which would also move the logger file to the markbind lib

[nbriannl]

What shall i renamed the issue as?

Edit: Renamed

[nbriannl]

This behavior no longer appears due to the mocking of the entire logger module in #1117, However, it would be more ideal if we use mocked and unmocked instances of fs in appropriate sections.

[ang-zeyu]

Resolved by #1207

Yet to un-mock logger in Parser.test.js