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
There doesn't seem to be a handler trait that clearly establishes an interface between the application and the user handler functions.
At our company, we created a tracing_rocket crate which allows for open telemetry spans (by implementing additional features in the macros) from the code calling the user defined handler.
We use that, instead of the rocket macros that generate handlers.
When you combine that (not having a contract) with the fact that part of the application routing is happening inside the generated handler (forwarding), it leaves a lot of room for our crate breaking on a "non breaking change" in rocket.
The text was updated successfully, but these errors were encountered:
There doesn't seem to be a handler trait that clearly establishes an interface between the application and the user handler functions.
At our company, we created a
tracing_rocket
crate which allows for open telemetry spans (by implementing additional features in the macros) from the code calling the user defined handler.We use that, instead of the rocket macros that generate handlers.
When you combine that (not having a contract) with the fact that part of the application routing is happening inside the generated handler (forwarding), it leaves a lot of room for our crate breaking on a "non breaking change" in rocket.
The text was updated successfully, but these errors were encountered: