Affected by core regression issue on no route match?

I prepared a MR with the code from the core issue.
But we should also please carry over the tests to our tests to ensure it works as expected.

I used patch #36 as basis, let's now postpone this on the core issue and see what's the final outcome there. If anyone

@Grevil could you please carry over the tests from #36 in https://www.drupal.org/project/drupal/issues/3348592 🐛 [regression] Language switcher block throws exception when no route is matched Fixed into this issue?
I think our block should just behave the same.

Funny, in the added tests in https://www.drupal.org/project/drupal/issues/3348592 🐛 [regression] Language switcher block throws exception when no route is matched Fixed , they implemented the tests, like they are logged in as an anonymous user, but instead, they are logged in as an "admin" account which is not completely admin, so the tests still succeed.

Also, they check if the label of the block exists on a 403 page? That is super weird... Setting this to needs work, as it seems I do not understand the tests.

@Grevil: If you're sure, please leave a note at the core issue.

Settings this back to PP on the core issue for now. Thanks for your work on this!

seems like this is not an actual error/bug report, but a related concern about how/when core may change 'something' (:

closing. no proof.

I guess we should still add the tests implemented in the core issue? Since the "no route matched" problem could also appear in our module due to some regression problems in the future?

FYI, @Anybody one of the core maintainers approved my problem, mentioned in #8, I created a follow-up issue, as expected by him: 📌 Partially refactor Language switcher block tests Active .

@Grevil nice!! :)

Yes, I agree with #12! Separate issue?