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
It would be nice to have an option in debug() that skips printing props in the debug string.
For large components with many props spread across the different elements in the render tree, if you want to focus on the structure of the tree when debugging, this option can hide all props so you can focus just on the hierarchy of elements.
This is particularly useful if matchesElement() is used in a test that fails. matchesElement() just returns a boolean that doesn't show the diff of what didn't match when it fails. Using debug() is the best way to debug this. However, matchesElement() ignores props in its comparison, so it would be nice to have a variant of debug() that also ignores props so that it can be used while debugging to figure out exactly what is the diff between actual and expected values that caused matchesElement() to fail.
The text was updated successfully, but these errors were encountered:
It would be nice to have an option in debug() that skips printing props in the debug string.
For large components with many props spread across the different elements in the render tree, if you want to focus on the structure of the tree when debugging, this option can hide all props so you can focus just on the hierarchy of elements.
This is particularly useful if matchesElement() is used in a test that fails. matchesElement() just returns a boolean that doesn't show the diff of what didn't match when it fails. Using debug() is the best way to debug this. However, matchesElement() ignores props in its comparison, so it would be nice to have a variant of debug() that also ignores props so that it can be used while debugging to figure out exactly what is the diff between actual and expected values that caused matchesElement() to fail.
The text was updated successfully, but these errors were encountered: