Components that render `null` cause `Cannot read property 'nodeType' of undefined` about cypress-react-selector HOT 9 CLOSED

Hi @laurence-myers , if it is undefined what output Node information you want to get from the .react()?

Can you suggest any sample output structure?

from cypress-react-selector.

Sorry, I'm just learning Cypress, so I'm not really sure how the API should work. 🙁 Maybe I'm using it incorrectly. I was hoping calling .react('ErrorMessage').should('not.be.visible') would check for existence of the node, but maybe I should be asserting .should('not.exist') or similar? I'll double check if that works.

from cypress-react-selector.

Thanks @laurence-myers . Let us know if that works.

from cypress-react-selector.

Hi @laurence-myers , any update you like to share?

from cypress-react-selector.

closing due to staleness.

from cypress-react-selector.

.should('not.exist') doesn't work either. I'm trying to assert that there are 0 AccountCards on the page.

cy.react("AccountCard").should('not.exist') throws

Timed out retrying: Expected to find element: undefined, but never found it.

I also tried cy.react("AccountCard").should("eq", undefined);, but that returns the same error.

from cypress-react-selector.

After updating to v2.2.1, cy.react("AccountCard").should("not.exist") now throws:

@abhinaba-ghosh Any ideas for a workaround?

from cypress-react-selector.

so, the expectation is AccountCard should not exist right? I think it's not handled correctly now. Can you raise a ticket explaining the whole scenario?

from cypress-react-selector.

That's correct. I'll get some more info for you and open a new ticket.

from cypress-react-selector.