Sebastian Schuberth

Results 1476 comments of Sebastian Schuberth

Kotest plugin 1.3.86-243-EAP-SNAPSHOT was released already, which supports Intellij 2024.3 in K2 mode.

> I think it is not clear from the text in the README and the examples whether a `/` in the namespace needs to be escaped. I think it's rather...

> 1. "percent-encoded string" does not specify whether `/` is supposed to be encoded or not. Then your definition of "percent-encoded" seems to differ from mime, and what [Wikipedia](https://en.wikipedia.org/wiki/Percent-encoding) says:...

> Percent encoding lists no reserved characters Ok, let me see: ![image](https://github.com/user-attachments/assets/d504c528-b52f-414b-9a3b-6e70e1ecb5c9) ![image](https://github.com/user-attachments/assets/1b5208f2-2709-424e-a609-b1409bbe0654) > `/` is a reserved character in a URI Right, and [a PURL actually is a URI](https://github.com/package-url/purl-spec/blob/master/PURL-SPECIFICATION.rst#a-purl-is-a-url)....

> You're apparently looking at a different Wikipedia. Well, it would be easier to tell if you provided any links like I did. Unless there was some irony involved from...

> As I said before, "percent-encoded" does not mean that particular characters are or are not encoded. Ok, but when talking about "percent-encoded" in PURL-context it should always mean the...

> It'd be nice if the spec said exactly which characters were supposed to be escaped when instead of saying which sometimes-escaped characters should not be escaped. Absolutely! Just calling...

> `pkg:golang/github.com%2Fquic-go%[email protected]` is a valid PURL with no namespace. It is not equivalent to `pkg:golang/github.com/quic-go/[email protected]`. Exactly. While both are valid purls syntax-wise, the former interprets the whole string "github.com/quic-go/quic-go" as...

> I think the unfortunate thing is that PURL has a general concept of namespaces at all. Also see https://github.com/package-url/purl-spec/issues/14. > From my perspective, package types with meaningful namespaces are...

> Thank you for this PR @maxhbr . When you have the chance, could you please merge the latest master into this branch? I've simply rebased the PR from the...