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
When a middleware returns an error, then metadata.env struct doesn't have status, body, headers etc, while these fields were available in the middleware. I'd expect to have this data in telemetry handler, as it helps in debugging.
Script:
Mix.install([:tesla,:telemetry]):telemetry.attach_many("tesla.request",[[:tesla,:request,:stop]],fn_event,measurements,metadata,_->dbg(metadata)end,nil)defmoduleExpectOKMiddlewaredo@behaviourTesla.Middleware@implTesla.Middlewaredefcall(env,next,_opts)dowith{:ok,env}<-Tesla.run(env,next)doifdbg(env).status==200do{:ok,env}else{:error,{:unexpected_response,"not ok :("}}endendendendclient=Tesla.client([Tesla.Middleware.Telemetry,{Tesla.Middleware.BaseUrl,"https://hex.pm/api"},ExpectOKMiddleware])client|>Tesla.get("/packages/tesla")|>dbg()
When a middleware returns an error, then
metadata.env
struct doesn't have status, body, headers etc, while these fields were available in the middleware. I'd expect to have this data in telemetry handler, as it helps in debugging.Script:
output:
The text was updated successfully, but these errors were encountered: