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
Let me paste the message here because it's gone after 90 days. 😢
what do you all think about naming these Runnables, Callables and such so we return ContextAwareRunnable , ConextAwareCallable and so on, just like we do with ContextAwareFuture already. I have a use-case when I need to access runnable.context() for $reasons.
…iFunction (#4890)
Motivation:
Users of Armeria APIs might need to be able to query the underlying
`RequestContext` attached to a given "context-aware" `Runnable` or
`Callable`. Let's name these anonymous classes and give then structure.
Modifications:
- Introduce two new interfaces: `ContextAwareRunnable`,
`ContextAwareCallable`
- Introduce two new implementations: `DefaultContextAwareRunnable`,
`DefaultContextAwareCallable`
Result:
- Closes#4878
More context in Slack: https://line-armeria.slack.com/archives/C1NGPBUH2/p1684259957145409
The text was updated successfully, but these errors were encountered: