Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has acontribution guide which I suggest you to read.

In short:

• Always add tests
• Keep backward compatibility (seehttps://symfony.com/bc).
• Bug fixes must be submitted against the lowest maintained branch where they apply (seehttps://symfony.com/releases)
• Features and deprecations must be submitted against the 7.1 branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

Can you elaborate what kind of duplicate code you need to write currently because the method is not public? I'm not convinced yet, we need this change.

Generally speaking, the method was not intended to be a public API which is why it's just a private method on the validator. If we wanted to make is reusable, we should rather extract it into a separate service that can be consumed in userland as well.

Either way, we would need additional tests. Your change creates a new public API that is not covered by tests currently.

im wondering if the strenght value should be set as a violation parameter, so it can be obtained or used in translations using existing public API

good idea, see#54479