packagecontrol / packagecontrol/thecrawl
Libraries releases' version field description
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 4h 53m
- Merged PRs (30d)
- 14
Description
With regards to https://github.com/packagecontrol/thecrawl/blob/a42b390b4b90937a7637d635bbb939528b753d55/lib-spec.md?plain=1#L98-L100
Package Control 4 treats packages and libraries more or less equally with regards to meta data. This means the version key in a repository is dedicated to url based releases. It is not intented to be a PEP440 version specifier (e.g. >=1.0.0). It must not appear together with asset, base, tags or branch keys.
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
Read lib-spec.md around lines 98-100 and compare the current description of the version field with the issue's Package Control 4 behavior. Update the documentation to describe URL-based releases, distinguish it from PEP 440 specifiers, and state that it must not be combined with asset, base, tags, or branch; verify the surrounding specification remains consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100