@epriestley are code contributions no longer accepted? We don't consider this something related to a bug report per se.

See Contributing Code.

The barrier for contributions is extremely high. In almost all cases where users write code nowadays, it would save us time if they just reported a bug with reproduction instructions instead, since we almost always need this information anyway and sending a patch without this information just adds more overhead.

This is probably one of those cases. There's no associated task describing what the actual problem is, and from the description alone, I don't really know what problem this solves, how to reproduce the issue, etc. Since I don't know what the actual goal is here, I'm not really sure if this is a reasonable fix or not.

Offhand, I'd guess it probably isn't the best fix we could come up with. One aspect of this change which I'm uneasy about, and which might be a bit of a red flag, is that we're destroying information fairly early in the pipeline. Often, it's better to preserve information for as long as possible and normalize it at the last moment. I'm not sure if that applies here or not, but I'd want to look at ways we might be able to retain the original path information for as long as possible.

See also Planning.