Consider 'Forbidden' as built-in error type about error-or HOT 4 CLOSED

For me it would make sense to change "Unauthorized" to "Forbidden" because .net is handling authentication for me and authorization is done in layers where I use ErrorOr, but I can't say if that is the case for alle developer which use ErrorOr.

I think Unauthorized could still be useful for developers which roll there own authentication so maybe Forbidden could be added instead of replacing Unauthorized. Adding will also maintain backwards-compatibility.

from error-or.

Hey guys. I intended the "Unauthorized" to mean the user failed some authorization step (not authentication).

I understand why this is confusing given 401 is "Unauthorized" and not "Unauthenticated".

Perhaps "Forbidden" would have been a better name choice. I can rename "Unauthorized" to "Forbidden" if you think it is worth the change, but please note this would be a breaking change.

Let me know would you think.

from error-or.

I would also like this so I created a PR (I did not see there was already an open PR for this so I am happy with any merge)

from error-or.

added #86

from error-or.