You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an endpoint that looks like /Users/v2/<uuid>. I would like to use Capture "id" UUID in my API types (for documentation purposes), but when the UUID is unparseable, I want the API user to get 401, not 404. It would be nice if I could say Capture' [Lenient] "id" UUID and then get an Either Text UUID in my handler and deal with it myself.
Does that make sense?
The text was updated successfully, but these errors were encountered:
I have an endpoint that looks like
/Users/v2/<uuid>
. I would like to useCapture "id" UUID
in my API types (for documentation purposes), but when the UUID is unparseable, I want the API user to get 401, not 404. It would be nice if I could sayCapture' [Lenient] "id" UUID
and then get anEither Text UUID
in my handler and deal with it myself.Does that make sense?
The text was updated successfully, but these errors were encountered: