Frank Dekker

> > > Just want to point out that this implementation doesn't baseline individual violations. Instead, it baselines specific sniffs for specific files. Which is different from what one might...

> > > I'm not convinced that this is a useful way of doing a baseline. When entire sniffs (or even sniff codes) are baselined for a file, adding new...

@gsherwood Improved the baseline calculation based on the approach I suggested in #2543 Now a code signature will be calculated and added to the baseline report file. The code signature...

@gsherwood It's been a while. You had any chance yet to look at the latest proposal with the code signatures?

> Being able to have a baseline would be much appreciated. > > Is there anything that can be done to move this forward? @Potherca At our company we really...

> Is there a chance to see this PR merged? It would be really useful for us too, especially when working with big codebases. You can use https://github.com/123inkt/php-codesniffer-baseline in the...

In reference to #3387 ### Problem: Find a way to uniquely identify where a violation originated from. **Options:** - Using line numbers is a no go as modifications to the...

@kylekatarnls Hi, we're also slowly preparing to switch projects to PHP8.1. I ran into the issue that pdepend doesn't yet support pure intersection types. I haven't dipped into pdepend yet....

Is this still open for implementation? I _might_ be interested in adding a result caching feature. **Flags:** `--cache` or `--cache=.phpmd.cache.php`. will default to `.phpmd.cache.php` if `--cache` is used **Store:** -...

> That would be fantastic! > > PHP version is probably best to have in there as there are feature levels that won't be analyzed if not supported. Though it...