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
Replace ellipses with number of items that can be expanded. #128
Comments
That's an interesting idea. I'll try it out and see if it's confusing. |
I'm doing this with CSS, so it's hard to do the count. |
I think it would be better to inline all child items, possibly grayed out, cutting off to a single (the first) line, possibly using |
Haven't had the time to look into implementing this into a PR but here's what I mean:
Collapsing the view further:
To implement this I'll need to add |
I like that! Would you be able to send a PR for it? The only thing to keep in mind is that copy-paste should preserve valid JSON. |
This is related to #131. |
I'm able to prepare a PR for it, now that I have some free time on my hands, but I've played with it a bit more, and realized the original formatting could not be kept as currently is (on copy+paste) as the collapsed nested content would be forced inline. If that's not absolute showstopper(?) I will go ahead and prepare a PR for this. May be we could have this behavior behind a preference? |
Thanks for taking a look! I'll see if I can get some free time this weekend to go over what you're proposing.
…-Ben
On Dec 30, 2016, at 7:15 AM, Stanimir Stamenkov ***@***.***> wrote:
@bhollis:
I like that! Would you be able to send a PR for it?
The only thing to keep in mind is that copy-paste should preserve valid JSON.
I'm able to prepare a PR for it, now that I have some free time on my hands, but I've played with it a bit more, and realized the original formatting could not be kept as currently is as the collapsed nested content would be forced inline. If that's not absolute showstopper(?) I will go ahead and prepare a PR for this. May be we could have this behavior behind a preference?
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
for example
change:
to
The text was updated successfully, but these errors were encountered: