Skip to content

Support strict comparisons #247

Open
@mattfarina

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).

  1. If there is a == there should be a !== to complement it
  2. There should be a way to do strict comparisons with build metadata taken into account and with it skipped
  3. 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).
  4. 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 ==1 will NEVER match to anything because a version would be 1.0.0 and a strict string comparison between those would be different.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions