-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
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
Regression in v0.2.7 #31
Comments
Hmmm, your choice but I personally think 100 is too harsh a limit. Browser console is for debugging purposes, not for UI. Your library is for UI. I've had to go back to version 0.2.6 and if you don't plan on supporting 100+ rows without the user having to uncollapse then I'll need to move libraries. |
Don't worry, I hope I'd give you a satisfactory reply. Thanks for your issue feedback. |
@shennan new property |
There is a change in the way that auto-collapsing of objects works between version 0.2.6 and 0.2.7.
When handing it a large array, v0.2.7 auto-collapses the array into sections of 100; like so:
Which is not great. This happens even if I set the
collapseObjectsAfterLength
prop to higher than 100 or remove it entirely.Have a test yourself on this:
It's worth noting that the version before (0.2.6) doesn't do this but it also doesn't respond to the
collapseObjectsAfterLength
property at all - so it could be that this is just an issue with displaying arrays at the root level?If the intention is to have an absolute maximum before collapsing, then 100 is too low of a setting. In any case; some clarity in the docs would be preferable (if this is not a bug).
The text was updated successfully, but these errors were encountered: