-
Notifications
You must be signed in to change notification settings - Fork 172
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
base: main
Are you sure you want to change the base?
Conversation
Supercedes package-url#52 Signed-off-by: Jeremy Long <jeremy.long@gmail.com>
bb7f3f3
to
cdafe25
Compare
@@ -252,7 +252,7 @@ | |||
"is_invalid": false | |||
}, | |||
{ | |||
"description": "slash /// after type is not significant", | |||
"description": "leading slash /// in front of type is not significant", |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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////:
There was a problem hiding this comment.
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. 👍
There was a problem hiding this comment.
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.
Corrected copy-paste issue in the description of the test for /// (test-suite-data.json:255).