-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Http endpoint base class with request context access #18
Conversation
# Conflicts: # akka-javasdk/src/main/java/akka/javasdk/http/RequestContext.java # akka-javasdk/src/main/scala/akka/javasdk/impl/SdkRunner.scala
0f6b24f
to
06cda58
Compare
/** | ||
* Optional base class for HTTP endpoints giving access to a request context without additional constructor parameters | ||
*/ | ||
abstract public class AbstractHttpEndpoint { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatively, we could call it RequestContextSupport
.
And maybe better if we make this a interface with default methods. As such users can use it as a mixin instead.
And have some other base classes on their own.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need a field so interface does not work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yes, that's true.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* feat: Http endpoint base class with request context access # Conflicts: # akka-javasdk/src/main/java/akka/javasdk/http/RequestContext.java # akka-javasdk/src/main/scala/akka/javasdk/impl/SdkRunner.scala * post rebase fixes * formatting...
Only showcased on ACL and JWT doc pages so far, once we add header support, it will go on the HTTP endpoint page as well.