-
Notifications
You must be signed in to change notification settings - Fork 35
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
feat(config): refresh stale prefs #88
base: main
Are you sure you want to change the base?
Conversation
feat(settings): refresh state
This PR is stale because it has been open 30 days with no activity. |
. |
This PR is stale because it has been open 30 days with no activity. |
. |
This PR is stale because it has been open 30 days with no activity. |
. |
This PR is stale because it has been open 30 days with no activity. |
. |
This PR is stale because it has been open 30 days with no activity. |
This PR is stale because it has been open 30 days with no activity. |
. |
feat(settings): refresh state
Description
The state of the plugin internally does not always reflect the local and global config files. For example, if I define a an exclusions property in my local config, then load everything with neoconf. Then I remove an item and use neoconf.get(), it will return the old state of the config. Using this refresh method re-fetches the items from the local and global file.
I need this because I created a binding in neotree to toggle a node as excluded. I change the highlights as excluded using the component field:

However this would never work properly without me being able to reset the internal state so that the item is removed from neoconf.
Now each time I invoke the binding that toggles this, the node is correctly toggled from the exclusions list in the local config file using my own separate json parsing.
Related Issue(s)
#61 61
Screenshots