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
In the docs this is described as: "Handler represents a Plugin endpoint.". We started discussing whether this comment was correct or not and were discussing whether the Handler should be renamed to PluginEndpoint or just Endpoint.
Some assessment suggests that the comment might be wrong, but that turned into a different proposal that we believe is worth chasing:
The proposal here is that it becomes private. For plugins that still want to do this, the plugin can simply return a box service rather than returning a handler created from a box service. The original design seems to suggest (@bnjjj may be able to a provide a link to context here) that we introduced the previous pattern because of a constraint imposed by Warp, that is no longer necessary with our change to Axum.
The text was updated successfully, but these errors were encountered:
In the docs this is described as: "Handler represents a Plugin endpoint.". We started discussing whether this comment was correct or not and were discussing whether the
Handler
should be renamed toPluginEndpoint
or justEndpoint
.Some assessment suggests that the comment might be wrong, but that turned into a different proposal that we believe is worth chasing:
The proposal here is that it becomes private. For plugins that still want to do this, the plugin can simply return a box service rather than returning a handler created from a box service. The original design seems to suggest (@bnjjj may be able to a provide a link to context here) that we introduced the previous pattern because of a constraint imposed by Warp, that is no longer necessary with our change to Axum.
The text was updated successfully, but these errors were encountered: