Fix: Debug.LogError annotation point not parsed correctly

[12joan]

Changes

Correctly parse the annotation point for stack traces created by Debug.LogError.

Related Issues

Fixes #278

Successfully Failed Workflow Run Link

Note that the RuntimeUtils.cs:580 annotation (Debug.LogError) and the TestHelpers.cs:130 annotation (Assert.Fail) are both reported correctly.

https://github.com/anderbellstudios/pop-pixie/actions/runs/10002797271/job/27648683312#step:4:21445

Checklist

• Read the contribution guide and accept the code of conduct
• Docs (If new inputs or outputs have been added or changes to behavior that should be documented. Please make a PR
  in the documentation repo)
• Readme (updated or not needed)
• Tests (added, updated or not needed)

[github-actions]

[GabLeRoux]

Explanation of Regex Changes

Original Regex:

/at .* in ((?<path>[^:]+):(?<line>\d+))/

Updated Regex:

/at(?: .* in)? ((?<path>[^:]+):(?<line>\d+))/

Changes Explained:

1. Introduction of Non-Capturing Group:

   • Original: at .* in
   • Updated: at(?: .* in)?
   • Explanation: The non-capturing group (?: .* in)? makes the .* in part optional. This change allows matching lines that do not strictly follow the "in" keyword structure.

2. Regex Application:

   • Original: trace.match(/at .* in ((?<path>[^:]+):(?<line>\d+))/g);
   • Updated: trace.match(new RegExp(regex, 'g'));
   • Explanation: The regex is now reused with new RegExp(regex, 'g'), improving code maintainability by storing the regex pattern in a variable.

Purpose of Changes:

These updates improve the flexibility and robustness of the findAnnotationPoint function, allowing it to correctly parse a wider variety of stack trace formats, including those generated by Debug.LogError.

---

Looks good to me 👍