[RuleDocGenerator] Link rule class to source

[ruudk]

Fixes rectorphp/rector#5476

Is this the right approach? If so, I can fix the PHPStan errors.

[TomasVotruba]

Looks good. How does it work on split package?

[ruudk]

How do you mean? How it looks on Rector's side?

[TomasVotruba]

In split package of Symplify monorepo, like:

• https://github.com/symplify/phpstan-rules/blob/master/docs/rules_overview.md
• https://github.com/symplify/coding-standard/blob/master/docs/rules_overview.md

[ruudk]

How to test?

[TomasVotruba]

It looks it's tested correctly on split package: https://github.com/symplify/symplify/pull/2956/checks?check_run_id=1903101376 👍

Just tests need an update to differ between monorepo run and split run.
Check tests/bootstrap.php - there is a constant that is present only monorepo tests: https://github.com/symplify/symplify/blob/1353bd6ae212d520f7b7a43902e83edae8c91bcb/tests/bootstrap.php#L21

[TomasVotruba]

Btw, were using naming convention for pull-request, like [PackageName] The title.
That way we can automatically generate per-package changelog once a week, without much effort.

Could you use this convention in PRs so these pull-request will be assigned to right packages?
Thank you

[ruudk]

@TomasVotruba It's ready now 🎉 ✅

[TomasVotruba]

Looks good, thank you 👍