-
Notifications
You must be signed in to change notification settings - Fork 252
feat: configurable indent marker level #1570
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
Conversation
7f67024
to
86a78c5
Compare
86a78c5
to
79ba9e5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one is questionable. I don't know for sure, but other code may assume that level 0 means the root node and this could be more than just a visual tweak.
There is also a padding option on the container which may be more appropriate. Either way, see: #1606
@pynappo could this be merged? i use this for a while now without issues |
I would like this merged too. Any way in which I could contribute? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd say this is good
Gladly! Feel free to create a PR against this branch or rebase it and open a new PR, then ill close this one.
There are still some issues in there. This is described in: #1570 (comment) |
Yes, this is what the issue is about. I like how it looks. Perhaps this is fixable with an
Not sure either, could send what you already have? Maybe someone could help out with it? |
Alright if you like the node 0 implementation, I'd say we leave it like that, I don't even think a conditional would be necessary, and it would allow for more customization, anyone could decide if they want the indent marker from the node 0 with or without the root node hidden. I also recommend calling the option, I was wondering if I could commit directly to this PR branch, or if another PR is needed, I appreciate the guidance. |
both is fine |
alright, I just made a new PR #1705 with the changes we discussed here. feel free to test them |
closing in favour of: #1705 |
closes #1512