Skip to content

Conversation

@nnethercote
Copy link
Contributor

I missed some cases in #13.

In JSON mode, an input filename like `c:\\foo\\bar\\baz` currently isn't
unescaped. This has two effects.
- Lookup will use `c:\\foo\\bar\\baz` instead of `c:\foo\bar\baz`. This
  doesn't cause problems because repeated separators are treated the
  same as single separators, but it is clumsy.
- If the file has errors, error messages will say `c:\\foo\\bar\\baz`
  rather than `c:\foo\bar\baz`. Again, understandable but clumsy.

This commit fixes this by unescaping input filenames in JSON mode.
@nnethercote nnethercote merged commit b0abef0 into mozilla:master Mar 3, 2020
@nnethercote nnethercote deleted the fix-JSON-handling-more branch March 3, 2020 22:58
@nnethercote
Copy link
Contributor Author

@gabrielesvelto: And once again, I already landed this because I needed it in a hurry for https://bugzilla.mozilla.org/show_bug.cgi?id=1604095, but I'd be interested to hear if you have any review comments. Thanks.

@gabrielesvelto
Copy link
Collaborator

LGTM just like the previous fix. I ran myself into this kind of stuff when dealing with JSON in crash annotations and it's always annoying to have to selectively unescape stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants