We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Will create a repro if needed.
The code in https://github.com/nolimits4web/swiper/pull/5954/files#diff-88a223b4c7649642379e3d1da5338dc2432bbe32b5787cfcda0b484fce3e3786 is causing me issues because there is a circumstance where displayName is null, and since there is no check for && child.type.displayName in the if statement, I'm getting a Cannot read property 'includes' of undefined when that situation is encountered.
displayName
&& child.type.displayName
Cannot read property 'includes' of undefined
Check succeeds without error.
TypeError: Cannot read property 'includes' of undefined
8.4.0
React
The text was updated successfully, but these errors were encountered:
I can confirm the issue is valid, as quick workaround we had to use swiper 8.3.2 version.
Sorry, something went wrong.
Same problem here...
TypeError: e.type.displayName is undefined
37a94ea
Thanks for the quick response!
No branches or pull requests
Check that this is really a bug
Reproduction link
Will create a repro if needed.
Bug description
The code in https://github.com/nolimits4web/swiper/pull/5954/files#diff-88a223b4c7649642379e3d1da5338dc2432bbe32b5787cfcda0b484fce3e3786 is causing me issues because there is a circumstance where
displayName
is null, and since there is no check for&& child.type.displayName
in the if statement, I'm getting aCannot read property 'includes' of undefined
when that situation is encountered.Expected Behavior
Check succeeds without error.
Actual Behavior
TypeError: Cannot read property 'includes' of undefined
Swiper version
8.4.0
Platform/Target and Browser Versions
React
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: