Skip to content

feat: add support for plugins#135

Draft
RobertCraigie wants to merge 1 commit into
mainfrom
feat/plugins
Draft

feat: add support for plugins#135
RobertCraigie wants to merge 1 commit into
mainfrom
feat/plugins

Conversation

@RobertCraigie
Copy link
Copy Markdown
Member

@RobertCraigie RobertCraigie commented Dec 5, 2025

TODOs:

  • For plugin authors section in the docs
  • Spell docs out way more
  • should this be opt-in? e.g. glide.plugin_search_roots = glide.plugins.default_search_roots?
  • what should the default search roots be?
  • handle errors better
  • provide a __filename or import.meta.url so that plugins can know their current file path
  • more concurrency when loading
  • autocmd for pre plugin load?
  • make nested glide.unstable.include() support relative paths relative to the file being loaded
  • Should probably have an allowlist of plugins to be loaded? with a confirmation dialog when we find a new one

TODOs:
- [ ] For plugin authors section in the docs
- [ ] Spell docs out way more
- [ ] should this be opt-in? e.g. `glide.plugin_search_roots =
glide.plugins.default_search_roots`?
- [ ] what should the default search roots be?
- [ ] handle errors better
- [ ] provide a __filename or import.meta.url so that plugins can know
their current file path
- [ ] more concurrency when loading
- [ ] autocmd for pre plugin load?
- [ ] make nested glide.unstable.include() support relative paths
relative to the file being loaded
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant