-
Notifications
You must be signed in to change notification settings - Fork 37
feat(config): provide user callback on live reload #87
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
base: main
Are you sure you want to change the base?
Conversation
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. |
. |
This PR is stale because it has been open 30 days with no activity. |
Description
It's useful to be able to do some work once the plugin has live_reloaded after a local or global config file has been written to.
For example: I define a list of "exclusions" similar to IntelliJ so that files and folders that match this pattern, are excluded from text searches, the folder is marked as excluded in the file tree etc. In IntelliJ this takes effect immediately when you mark a file or folder as excluded.
I'd like to mimic this behaviour using this plugin, so by providing a callback, I can do so.
Telescope defines these exclusions in
config.defaults.file_ignore_patterns
. So with this callback, I can call the setup function again by setting this value with the newly updated value from neoconf via.get("exclusions")
.This is just a simple example, there are many applications for this callback.
#65
Related Issue(s)
#65
Screenshots