package-url / packageurl-go

89%

master: 89%

LAST BUILD ON BRANCH type-constants

branch: SELECT

CHANGE BRANCH

x

Sync Branches

• No branch selected
• 59-add-knowntypes
• TestSuiteData
• add-pub-bitnami-types
• add-vcpkg-type
• benji.visser/remove-deprecated-ioutil-usage
• cpan-optional-namespace
• dot-slash-valid-subpath-prefix
• escape
• feat/add-missing-purl-types-20230403
• fix-ci
• fix-failing-cpan-unit-test
• fix-failing-tests
• fix-subpath-percent-decode
• fix/encode-sub-delims-in-path-segments
• fix/npm-missing-name
• fix_tests
• fuzz
• go-mod-version
• homebrew-case-sensitive
• julia
• known-cpan
• license_link
• main
• master
• normalize
• npm-case-sensitive
• patch-1
• qualifiers
• refs/tags/v0.1.1
• refs/tags/v0.1.2
• refs/tags/v0.1.4
• refs/tags/v0.1.5
• refs/tags/v0.1.6
• support-input-version-with-slashes
• type-constants
• upstream_test_data

Build # 32344891965

Build Type

Pull #104

github

Committed by timofurrer

Commit Message

Make purl type identifiers constants

These are fixed spec identifiers, but as package-level vars any consumer
could reassign them and change parsing behaviour process-wide.

Leaving them untyped keeps this backwards compatible: every read-only
use still compiles, and assigning to a named string type now works too.
Only taking their address or reassigning them breaks, which is the point.

KnownTypes and CandidateTypes stay vars, since maps cannot be constants.

Pull Request Pull Request #104: Make purl type identifiers constants

Coverage Stats

424 of 475 relevant lines covered (89.26%)

681.05 hits per line