The Reply.Err() and RPCErrors.Filter() are useful functions to get the SevError level errors out, but some people may want to treat SevWarning as errors as well and doing it manually is a pain.
As not to add a bunch of alternative functions like RPCError.FilterWarn, Reply.ErrWarn() and Reply.ErrAll() this updates Filter and Err to take in a list of desired severity levels. If they are missing they go back to defaulting to SevError which is a sane default.
Breaking change:
The API for reply.Err() and RPCErrors.Filter() were changed as above. For most call sites this should be fine but anyone using this function in a interface or explicitly using it as a type will break.
ErrSevError was renamed to SevErrorErrSevWarning was reanmed to SevWarning
As the API is not yet stable these changes are ok and will become stabilized after 1.0.0
The
Reply.Err()andRPCErrors.Filter()are useful functions to get theSevErrorlevel errors out, but some people may want to treatSevWarningas errors as well and doing it manually is a pain.As not to add a bunch of alternative functions like
RPCError.FilterWarn,Reply.ErrWarn()andReply.ErrAll()this updatesFilterandErrto take in a list of desired severity levels. If they are missing they go back to defaulting toSevErrorwhich is a sane default.Breaking change:
The API for
reply.Err()andRPCErrors.Filter()were changed as above. For most call sites this should be fine but anyone using this function in a interface or explicitly using it as a type will break.ErrSevErrorwas renamed toSevErrorErrSevWarningwas reanmed toSevWarningAs the API is not yet stable these changes are ok and will become stabilized after 1.0.0