Masterminds / Masterminds/semver
Support strict comparisons
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 168
- PR merge metrics
- No merged PRs in 30d
Description
PR #243 suggested the idea of a strict comparison (i.e. ==) that does direct string comparisons. Stricter comparisons are a good idea. This issue captures some notes and requirements (for myself for later).
- If there is a
==there should be a!==to complement it - There should be a way to do strict comparisons with build metadata taken into account and with it skipped
- Consider comparisons to node-semver which does not expose it's
==and===functionality in the Comparator but it exists for direct use (and has for over a decade). - If a full semver is NOT provided a loose (dirty) handling should be enabled so that users get what they expect. If it's not loose than a
==1will NEVER match to anything because a version would be1.0.0and a strict string comparison between those would be different.
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 reviewing PR #243 and the issue's discussion of node-semver's Comparator behavior. Turn the four listed requirements into a settled strict-comparison API, including complementary operators, build-metadata handling, and loose handling of partial versions; done means the behavior and scope are agreed and testable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100