Incorrect nullable return values throughout various classes

[IvovdBruggen]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

13.2.0

Bug summary

There are multiple methods that now return nullable types, that can safely be removed. I think this is a good QOL fix and prevents unnecessery null checks in codebases.

Solution

Check for info messages from the compiler that mention that the nullable return type can safely be changed to a non-nullable return type

[github-actions]

Hi there @IvovdBruggen!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂