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
While working on a test case involving React.Suspense with a fallback component I noticed that getReact('Foobar').should('not.exist') complains as follows:
Component not found <Foobar> There can be multiple reasons for it. > Component never meant to exists. You are good to go.
Now, in case the "good to go" case, how can I switch off this complaint just for this getReact()? Switching off log in the options doesn't suppress the "moaning" (which otherwise is perfectly useful, but not here).
The text was updated successfully, but these errors were encountered:
While working on a test case involving
React.Suspense
with a fallback component I noticed thatgetReact('Foobar').should('not.exist')
complains as follows:Now, in case the "good to go" case, how can I switch off this complaint just for this
getReact()
? Switching off log in the options doesn't suppress the "moaning" (which otherwise is perfectly useful, but not here).The text was updated successfully, but these errors were encountered: