Binding

Passing Values to Arguments

For example, let's take the following simple procedure, where we pass two values for which we want to get the subtract:

{
    "jsonrpc": "2.0",
    "method": "math@subtract",
    "params": {
        "a": 4,
        "b": 2
    },
    "id": 1
}

In this case, we need to write something like the following in the handler:

public function subtract(Request $request) {
    return $request->get('a') - $request->get('b');
}

Automatic passing of arguments will be by name:

public function subtract(int $a, int $b): int
{
    return $a - $b;
}

This will also work for deep things via camelCase:

{
    "jsonrpc": "2.0",
    "method": "....",
    "params": {
        "user": {
            "name": "Alex"
        }
    },
    "id": 1
}

for argument:

public function handler(string $userName): string
{
    return $userName;
}

Customizing The Resolution Logic

If you wish to define your model binding resolution logic, you may use the RPC::bind method. The closure you pass to the bind method will receive the value of the params segment and should return the instance of the class that should be injected into the route. Again, this customization should take place in the boot method of your application's RouteServiceProvider:

use Sajya\Server\Facades\RPC;
use Illuminate\Support\Facades\Route;

/**
 * Define your route model bindings, pattern filters, etc.
 *
 * @return void
 */
public function boot()
{
    RPC::bind('a', function () {
        return 100;
    });
}

This will automatically replace the substituted value in our method:

public function subtract(int $a, int $b): int
{
    return $a - $b; // $a = 100
}

But at the same time, the request will contain the original value that was passed.

Explicit Model Binding

To register an explicit binding, use the RPC::model method to specify the class for a given parameter. It would help if you defined your explicit model bindings at the beginning of the boot method of your RouteServiceProvider class:

use Sajya\Server\Facades\RPC;
use Illuminate\Support\Facades\Route;

/**
 * Define your route model bindings, pattern filters, etc.
 *
 * @return void
 */
public function boot()
{
    RPC::model('user', User::class);
}

It will work for anyone who expects a $user argument, and that value will be passed. The model will run the resolveRouteBinding method.

Deep binding

As with automatic substitution, bindings RPC::bind and RPC::model can be set for nested elements. To do this, you need to use the dot notation in the declaration. For example:

RPC::model('user.order', ...);
RPC::bind('user.order', ...;

In turn, this will expect camelCase in the arguments:

public function handler($userOrder)