[6.x] Fix migration class duplicate check

[ROOKIE20570]

Closes #30062.

[sisve]

This changes a method signature and may break existing code. Should it target another Laravel version?

[ROOKIE20570]

This changes a method signature and may break existing code. Should it target another Laravel version?

I am wondering if I can add another method to verify that it already exists, but that is not in line with the DRY principle.Let me think about it

[ROOKIE20570]

This changes a method signature and may break existing code. Should it target another Laravel version?

I added a default parameter, so the code that depends on this method can run

[gocanto]

Nice work ⭐

I added a default parameter, so the code that depends on this method can run

It might bring issues if somebody is extending this class since the given method is marked as protected.

You probably can extract the common path logic check from there, so you don't duplicate yourself. Therefore, this change can still be applied without breaking the API.

Nevertheless, you might want to wait for official feedback to keep working on it.

[taylorotwell]

While this does add an argument to a protected method, the likelihood of any given Laravel application extending this specific method seems pretty negligible to me.

[driesvints]

This broke the build. @ROOKIE20570 please make sure that the tests pass next time, thanks.

[ROOKIE20570]

This broke the build. @ROOKIE20570 please make sure that the tests pass next time, thanks.

Sorry, I was not familiar with it before, I will definitely do better next time.

[driesvints]

@ROOKIE20570 no worries at all 👍