Skip to content
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.

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

test: correct test description for leading slashes #365

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jeremylong
Copy link
Contributor

Corrected copy-paste issue in the description of the test for /// (test-suite-data.json:255).

Supercedes package-url#52

Signed-off-by: Jeremy Long <jeremy.long@gmail.com>
@jeremylong jeremylong mentioned this pull request Dec 10, 2024
@johnmhoran johnmhoran added Ecma specification Work on the core specification PURL miscellaneous slashes Covers slashes outside all of the PURL components, e.g., between 'pkg:' and the type value. labels Dec 11, 2024
@@ -252,7 +252,7 @@
"is_invalid": false
},
{
"description": "slash /// after type is not significant",
"description": "leading slash /// in front of type is not significant",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be slightly more accurate to say that "trailing slash after scheme should be removed" since it's more associated with that field than the schema.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or perhaps "all trailing slashes after scheme should be removed" ? BTW, do these descriptions need to refer to both the scheme and the colon ':' separator, since the slashes follow not just the scheme but the scheme and its colon separator? Or is that unneeded detail?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I used leading (or I suppose we could use preceding) because of the colon separator. If we said "trailing slash after schema" I think that would apply to pkg////:

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's how I'd interpret it as well. 👍

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ha, in pkg////: I understand pkg is the scheme field, //// are trailing slashes, and : is the separator between scheme and type :-) The separators, in my view, don't really belong to any of the components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ecma specification Work on the core specification PURL miscellaneous slashes Covers slashes outside all of the PURL components, e.g., between 'pkg:' and the type value.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants