Skip to content

Namespace: explicit parsing errors #455

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ppkarwasz wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Namespace: explicit parsing errors #455

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
aca3716
Namespace: explicit parsing errors
ppkarwasz Apr 8, 2025
7a97932
Replace `Signal` with `Report`
ppkarwasz Apr 15, 2025
58baca8
Merge branch 'main' into feat/path-parser-namespace
ppkarwasz Apr 15, 2025
9bd2568
Replace `solidus` -> `slash`
ppkarwasz Apr 15, 2025
b573897
Merge remote-tracking branch 'package-url/main' into feat/path-parser…
ppkarwasz Sep 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions PURL-SPECIFICATION.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -415,6 +415,7 @@ To parse a ``purl`` string in its components:
- Discard any empty segment from that split
- Percent-decode each segment
- UTF-8-decode each segment if needed in your programming language
- Report an error if any segment contains a solidus `/`
- Apply type-specific normalization to each segment if needed
- Join segments back with a '/'
- This is the ``namespace``
Expand Down