Do not log a warning when the errorBoundaryClass
is provided
#171
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a parcel is mounted it checks if
errorBoundary
is set or it implements thecomponentDidCatch
function, if those are not available it will log a warning to the console. This warning is always logged when you use theerrorBoundaryClass
property.It is possible to work around this by setting
suppressComponentDidCatchWarning
but that feels a bit weird, so this PR fixes this issue by include an additional check if theerrorBoundaryClass
is set