ProfessionalWiki / ProfessionalWiki/Maps
Don't include copies of JS libraries in the git repo
Open
Nobody has claimed this yet.
code quality
- Dominant language
- JavaScript
- Stars
- 78
- Forks
- 65
- Avg merge
- 9h 17m
- Merged PRs (30d)
- 6
Description
Seems like a good idea to use Composer or some other tool to automatically pull in the latest version...
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
Review the issue proposal and the linked drmonty/leaflet package first. Identify which JavaScript library copies are currently committed and how the repository could fetch them automatically; done means those copies are no longer maintained in the git repository and the dependency process is documented and repeatable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100