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
Is your feature request related to a problem? Please describe.
It's not convenient to write
id, err:=strconv.Atoi(c.PathParam("id"))
iferr!=nil {
returnnil, fuego.BadRequestError{
Title: "Invalid ID",
Detail: "The provided ID is not a valid integer.",
Err: err,
}
}
Is your feature request related to a problem? Please describe.
It's not convenient to write
see #372 (comment)
Describe the solution you'd like
From a user POV, we want 2 more functions in the context:
PathParamInt(name string) int
PathParamIntErr(name string) (int, error)
They will be used like this:
Additional context
Please add
Please mimic (and mutualise if it can be done nicely) what is done for
QueryParamInt
@dylanhitt should we add uint to handle case between max Int and max Uint, or is it too niche?
The text was updated successfully, but these errors were encountered: