External profiles
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 806
- Forks
- 434
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 32
Description
Is your feature request related to a problem? Please describe.
I would like to have 'external' profiles, creating a profile for my own documents requires me to have a profile in the official tree
Describe the solution you'd like
ideally build.js takes a parameter to allow inclusion from a directory outside the repo
Describe any alternatives you've considered
Fork the repo and merge the changes from the main line, although this works, it polutes the repository that only contains a profile.
Can you or your organization fund the work or help with development?
I'm willing to invest some time in this, I would need some feedback if this is a desired path
Contributor guide
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 with build.js, which the issue identifies as the entry point for adding an external profile directory. Trace how profiles are currently discovered and included, then determine how a directory outside the repository should be supplied and validated. Done means a profile can be included without forking or adding it to the official tree; no test file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100