Skip to content
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

[bug] node expansion inconsistent behaviour #485

Closed
brandon1024 opened this issue Aug 26, 2023 · 0 comments · Fixed by #486
Closed

[bug] node expansion inconsistent behaviour #485

brandon1024 opened this issue Aug 26, 2023 · 0 comments · Fixed by #486
Labels
bug Something isn't working

Comments

@brandon1024
Copy link
Contributor

I found a small quirk in how nodes are expanded/collapsed. I have some configuration that toggles expansion of a node or opens a leaf. This has stopped working correctly after updating the plugin.

	nmap <buffer> <CR> <Plug>(fern-action-toggle-expand-open)

	nmap <buffer><expr> <Plug>(fern-action-toggle-expand-open)
		\ fern#smart#leaf(
		\   "<Plug>(fern-action-open:select)",
		\   "<Plug>(fern-action-expand)",
		\   "<Plug>(fern-action-collapse)")

When I open Fern and expand a tree for the first time (with <CR>), it works as I would expect. After collapsing the node and expanding the tree again, the first child node is in the expanded state but doesn't render as such.

Here's a screen capture to demonstrate this behaviour. Notice the state of ews-eks when I expand it the second time:

Peek 2023-08-26 08-04

This was working correctly in cdec132 (Merge pull request #475 from lambdalisue/fix-viewer-auto-duplication, 2023-05-27), but stopped working after a rebase to d8c6698 (Merge pull request #484 from lambdalisue/fix-reveal, 2023-08-26).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants