micro-editor / micro-editor/micro
Accessing plugin directory
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
I'm not sure if I missed something in the docs; is there a better way to access the path of a plugin than hard coding it with config.ConfigDir .. "/plug/mypluginnamehere"?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how plugin paths are resolved around config.ConfigDir and the documented plugin-loading behavior. Determine whether an existing accessor is available or whether the request requires a new supported way to find a plugin directory; done means the supported approach is clear and no longer depends on hard-coded paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100