Hi there @tomvanenckevort, thank you for this contribution! 👍

While we wait for one of the Core Collaborators team to have a look at your work, we wanted to let you know about that we have a checklist for some of the things we will consider during review:

• It's clear what problem this is solving, there's a connected issue or a description of what the changes do and how to test them
• The automated tests all pass (see "Checks" tab on this PR)
• The level of security for this contribution is the same or improved
• The level of performance for this contribution is the same or improved
• Avoids creating breaking changes; note that behavioral changes might also be perceived as breaking
• If this is a new feature, Umbraco HQ provided guidance on the implementation beforehand
• 💡 The contribution looks original and the contributor is presumably allowed to share it

Don't worry if you got something wrong. We like to think of a pull request as the start of a conversation, we're happy to provide guidance on improving your contribution.

If you realize that you might want to make some changes then you can do that by adding new commits to the branch you created for this work and pushing new commits. They should then automatically show up as updates to this pull request.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

Hey @tomvanenckevort, thanks a lot for your PR to fix #19044 - someone on the core collaborators team will review this soon 😄

Hey @georgebid and @tomvanenckevort I will be having a look at this one.

Hey @tomvanenckevort I pushed some changes to make it non breaking. Could you test again on your end? For me it looked as the issue was still solved. Thank you for doing the hard work for me 🤗

@Migaroez Yes, that all works and looks good to me.
I hadn't taken into account that one of those changes was a breaking one, so thanks for sorting that out :)