#####   ######  #####    ###    #   #  ###  #   #  ######
##  ##  ##      ##  ##  ## ##   #   #   #   #   #  ##
#####   ####    #####   #   #   #   #   #   #   #  ####
##  #   ##      ##      ## ##    # #    #    # #   ##
##   #  ######  ##       ###      #    ###    #    ######

$ curl repovive.com/roadmaps/go/error-handling/using-errors-as

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░██████████████████████████████████████████████████████████████

#####   ######  #####    ###    #   #  ###  #   #  ######
##  ##  ##      ##  ##  ## ##   #   #   #   #   #  ##
#####   ####    #####   #   #   #   #   #   #   #  ####
##  #   ##      ##      ## ##    # #    #    # #   ##
##   #  ######  ##       ###      #    ###    #    ######

$ curl repovive.com/roadmaps/go/error-handling/using-errors-as

Repovive

Using errors.As - Error Handling | Go | Repovive

Repovive.

Go10 sections · 431 units20h total

Open in Course

Using errors.As

Type assertions on errors

Extract a specific error type with errors.As:

var ve ValidationError
if errors.As(err, &ve) {
    fmt.Println("Invalid field:", ve.Field)
}

errors.As searches the error chain for a matching type. If found, it sets your variable and returns true. This is safer than type assertions.