You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 13, 2024. It is now read-only.
I have kind of a problem. So when I'm using "enzyme" in my test files, the "debug" feature seems to ignore all my breakpoints. Everything else is working nice, tests pass and so on.
Without invoking any of the "enzyme" functions (shallow, mount), "debug" works as it should and stops on all breakpoints. But when I render anything, then it ignores every breakpoint.
I'm using "typescript", "react 17" and unofficial "@wojtekmaj eznyme adapter" (cuz official adapter hasn't come out yet).
When I run my tests via command line, vscode debugger pauses on breakpoints doesn't matter if I use enzyme or not.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi.
I have kind of a problem. So when I'm using "enzyme" in my test files, the "debug" feature seems to ignore all my breakpoints. Everything else is working nice, tests pass and so on.
Without invoking any of the "enzyme" functions (shallow, mount), "debug" works as it should and stops on all breakpoints. But when I render anything, then it ignores every breakpoint.
I'm using "typescript", "react 17" and unofficial "@wojtekmaj eznyme adapter" (cuz official adapter hasn't come out yet).
When I run my tests via command line, vscode debugger pauses on breakpoints doesn't matter if I use enzyme or not.
Beta Was this translation helpful? Give feedback.
All reactions