[New feature] Uses absolute path on checkstyle and junit report

[llaville]

Hello,

IMO, generate reports with relative paths is almost impossible to re-use in third-party tool context.

I actually works on a project that convert checkstyle format to another one (sarif), but I've noticed that Psalm 5.25.0 (latest version when I write this issue) still used relative paths on their reports.

While it's perfectly acceptable on github format (must not use the absolute path), it's not acceptable on others format like junit, checkstyle.

Working recently on phan and easy-coding-standard projects, both have ability to specify whatever we want to use absolute paths or relative paths.

• With Phan, and --extended-help panel we wan see the --absolute-path-issue-messages
• With ECS, we can see the new option withRealPathReporting() (https://github.com/easy-coding-standard/easy-coding-standard/pull/223)

I would like here to introduces a same feature flag for Psalm.

A PR will follows to share my contribution. Hope you'll accept it

[psalm-github-bot[bot]]

Hey @llaville, can you reproduce the issue on https://psalm.dev? These will be used as phpunit tests when implementing the feature or fixing this bug.

[llaville]

Hi guys @orklah , @danog, @weirdan

Is it possible to have a look on this request and related PR please ?

[llaville]

Is it possible to have an answer ?

[llaville]

Is this project dead ? No activity since ... https://github.com/vimeo/psalm/graphs/commit-activity