Method tagging lets you have more explicit control over which raw methods can match which real methods.
Example:
sealedtrait MethodType extends RpcTag
class GET extends RestMethod
class POST extends RestMethod
@methodTag[MethodType](new GET)
trait ExampleRawRpc {
@tagged[GET] def get(@methodName name: String, @multi args: Map[String,Json]): Future[Json]
@tagged[POST] def post(@methodName name: String, @multi args: Map[String,Json]): Future[Json]
}
In the example above, we created a hierarchy of annotations rooted at MethodType which can be used
on real methods in order to explicitly tell the RPC macro which raw methods can match it.
We also specify new GET as the default tag that will be assumed for real methods without any tag annotation.
Then, using tagged we specify that the raw get method may only match real methods annotated as GET
while post raw method may only match real methods annotated as POST.
Raw methods not annotated with tagged have no limitations and may still match any real methods.
Also, instead of specifying defaultTag in @methodTag annotation, you may provide the whenUntagged
parameter to tagged annotation. Raw method annotated as @tagged[MethodType](whenUntagged = new GET)
will match real methods either explicitly tagged with GET or untagged. If untagged, new GET will be assumed
as the tag. This is useful when you want to have multiple raw methods with different whenUntagged setting.
NOTE: The example above assumes there is a Json type defined with appropriate encodings -
see encoded for more details on parameter and method result encoding.
Method tagging lets you have more explicit control over which raw methods can match which real methods. Example:
In the example above, we created a hierarchy of annotations rooted at
MethodType
which can be used on real methods in order to explicitly tell the RPC macro which raw methods can match it. We also specifynew GET
as the default tag that will be assumed for real methods without any tag annotation. Then, using tagged we specify that the rawget
method may only match real methods annotated asGET
whilepost
raw method may only match real methods annotated asPOST
. Raw methods not annotated with tagged have no limitations and may still match any real methods.Also, instead of specifying
defaultTag
in@methodTag
annotation, you may provide thewhenUntagged
parameter to tagged annotation. Raw method annotated as@tagged[MethodType](whenUntagged = new GET)
will match real methods either explicitly tagged withGET
or untagged. If untagged,new GET
will be assumed as the tag. This is useful when you want to have multiple raw methods with differentwhenUntagged
setting.NOTE: The example above assumes there is a Json
type defined with appropriate encodings - see encoded for more details on parameter and method result encoding.
An example of real RPC for
ExampleRawRpc
:base type for tags that can be used on real RPC methods