Taking Maybe value directly about cleantickets

[aevitas]

Definitely see your point - what you suggest is also in line with the C# programming guidelines on that properties should always be safe to get, i.e. they are more similar to accessing a field than invoking a method.

Vladimir Khorikov's implementation in CSharpFunctionalExtensions takes this approach, but I found that more often than not, I don't actually have an action for the None() case. I do see how it would be safer to just invoke () => {} at runtime than throwing an InvalidOperationException just because some behaviour didn't net a value.

What do you typically provide for the empty value case in a Match call?

[megasuperlexa]

Depending on situation, e.g. the code here

CleanTickets/src/CleanTickets.Api/Program.cs

Line 40 in 719e70b

return result.HasValue ? Results.Ok(result.Value) : Results.NotFound();

could be:
return result.Match( success => Results.Ok(success), () => Results.NotFound();

But overall, this functional monadic stuff makes the whole codebase non-idiomatic, odd-looking and therefore hard to follow for ordinary C# people.
So instead of Maybe I would just use the standard C# language feature of Nullable reference types. What I typically do is turn them on as errors in the very beginning of a new project:

    <Nullable>enable</Nullable>
    <WarningsAsErrors>Nullable</WarningsAsErrors>

they're not without their issues, but are useful in the long run.