Go curations are creating new paths containing %2F instead of /

[capfei]

Recently I noticed when I tried to curate some go packages that it was creating new files with "%2F" as part of the path name instead using slashes like it did previously.

Example: https://github.com/clearlydefined/curated-data/pull/32403/changes

It tried to create a new file at curations/go/golang/golang.org%2Fx/crypto.yaml instead of updating /curations/go/golang/golang.org/x/crypto.yaml

[capfei]

I already fixed several in these PRs:

• Fix go paths curated-data#32404
• Fixing more go paths curated-data#32405

[pombredanne]

@capfei IMHO go is weird for their notion of module vs. package vs. file path where we cannot decide which start and ends at what slash.... but the choice to encode the slash in the namespace has been documented here:

• https://github.com/clearlydefined/clearlydefined/blob/25e527338c8f51a181503d13ded0838c9abaee87/docs/get-involved/using-data.md?plain=1#L113

And the code is there:

• service/lib/utils.ts

  Line 209 in f2469d0

  function reEncodeSlashes(namespace: string): string {

So if you remove them in curations, it may not work as expected? not sure though. The UI is playing games on me today.