Convert Model to JsonApi object in a custom Controller.

[chrisngabp]

Hello, I'd like to know if the package has any way to convert an object model to a json with the jsonapi structure in any controller (not necessarily an Eloquent jsonapi controller).

Thank you!

[lindyhopchris]

Hi!

Yes, extend the JsonApiController rather than the EloquentController. Then do something similar to what the EloquentController does in its methods, e.g the read method:
https://github.com/cloudcreativity/laravel-json-api/blob/master/src/Http/Controllers/EloquentController.php#L132

Note that you'll need to attach an adapter to so that all the parsing of the incoming request knows how to check whether a resource id is valid and can load the record that the id relates to. You need to extend the AdapterInterface and then list the full qualified class name in your json-api config file here:
https://github.com/cloudcreativity/laravel-json-api/blob/master/config/json-api.php#L130-L144

For an example of how this is done for Eloquent models, see this:
https://github.com/cloudcreativity/laravel-json-api/blob/master/src/Adapters/EloquentAdapter.php

I appreciate I really need to write some documentation... in the meantime feel free to ask any questions here.

[chrisngabp]

Hi lindyhopchris! thank you very much for your response!
I'll try to explain better what I need to do. My question was more like "how can I encode a Model to a JsonApi Object to print it in some view".
The example of what i'm trying to do: I want to have an encoded model printed in a view to use it as a preloaded object without having to make a request to the api.

EDIT: I have found a way of doing what I want using neomerx encoder like this:

`
use Neomerx\JsonApi\Encoder\Encoder;

(...)

$myModel = new MyModel();
Encoder::instance([
MyModel::class => MyModelSchema::class
])->encodeData($myModel);

`

Does laravel-json-api have a provider or a way to resolve something like I resolved with neomerx in the example??

[lindyhopchris]

Hi! Yes, that's the solution for the moment - manually create an encoder and then encode the data yourself.

I'm thinking that it would be really useful to have an approach (including a Blade directive) for outputting JSON API encoded data into a view. The use case you describe would be quite common in my opinion.

I'm going to leave this issue open as it's effectively a feature request!

[chrisngabp]

Thank you very much! It'll be great to have something like that in a future.

Another thing i've been trying to do and could be related to this in some way is to find a way to throw an exception or instance an error using the laravel-json-api errors.
Example: My controller (not a jsonapi one) receives a file via request and the file is not valid. Then I want to do something like "return RESOURCE_INVALID_ATTRIBUTES_MESSAGES".

Reference: https://github.com/cloudcreativity/laravel-json-api/blob/master/config/json-api-errors.php#L67

If you consider I can open another issue for this case :)

[lindyhopchris]

If you're using the ReplyTrait on your controller, you can return a string for the error. The string is the key that is defined in your JSON API errors config file.

So you can do the following on your controller:

return $this->reply()->error('my_error_key');

[GregPeden]

Just a +1 vote for this, I came here looking for a way to "consume" the API within the Laravel code base.

In my case, my web app is consuming its own JSON API for AJAX actions, and also I am using Laravel Echo to broadcast events. My app will have multiple people collaborating in the same space on separate devices, so other users need model events (create/edit/delete) broadcast to them. It would be swell for the broadcast JSON structure to follow the same format as the API does, because then I can use the same client-side code to process both cases (API response content and event broadcast content). Using your API package to do this ensures that in both cases the JSON structure would be identical even through design changes, which will make developmental do-it-by-myself testing more reliable.

[lindyhopchris]

Broadcast is definitely an aim. We're using broadcast at the moment but having to do it manually as follows:

    /**
     * Get the data to broadcast.
     *
     * @return array
     */
    public function broadcastWith()
    {
        /** @var CloudCreativity\JsonApi\Encoder\Encoder $encoder */
        $encoder = Encoder::instance([
            Post::class => Posts\Schema::class,
            Comment::class => Comments\Schema::class,
        ]);

        return $encoder->serializeData($this->post);
    }

Obviously what would be nicer is to have a more fluent way to do this, and get the encoder already loaded with the schema definitions that you set in your config.

If you are using the above as a temporary solution then remember to include in the array all the classes/schemas that could appear in the "tree" of resources that you are encoding.

[GregPeden]

That is really helpful, thanks!

[GregPeden]

Hello again.

I would like the Broadcast response to include the attributes within some of the relationships. For the life of me I cannot figure out how to make the attributes include the attributes on relationships. Any tips?

I have tried a bunch of stuff but here is how I have it set up at the moment.

    public function broadcastWith()
    {
        Log::info('Device event:', ['class' => self::class, 'data' => $this->device]);

        $this->device->load('building', 'type');
        return $encoder = Encoder::instance([
            Device::class => Devices\Schema::class,
            Building::class => Buildings\Schema::class,
            DeviceType::class => DeviceTypes\Schema::class
        ])->serializeData($this->device);
    }

In its schema:

    public function getRelationships($resource, $isPrimary, array $includeRelationships)
    {
        if (!$resource instanceof Device) {
            throw new RuntimeException('Expecting a Device model.');
        }
        return [
            'building' => [
                self::SHOW_SELF => true,
                self::SHOW_RELATED => true,
                self::DATA => $resource->building,
            ],
            'device-type' => [
                self::SHOW_SELF => true,
                self::SHOW_RELATED => true,
                self::DATA => isset($includeRelationships['device-type']) ?
                    $resource->type : $this->createBelongsToIdentity($resource, 'type'),
            ]
        ];
    }

whether or not I include "self::SHOW_DATA => true" above doesn't seem to affect the response when encoded in this way.

High-level this works, except the response is the top-level attributes on the Device object, and the attributes for Building and DeviceType are missing.

The log event is there just to prove that the Building model has the relationships loaded, even though I suspect the real intended method is to tell it to include the relationship by some other means.

[2017-04-22 05:18:20] local.INFO: Device event: {"class":"App\\Events\\Broadcasts\\Device\\DeviceEvent","data":"[object] (App\\Models\\Building\\Device: {\"id\":49,\"building_id\":2,\"device_type_id\":1,\"designation\":\"31\",\"slug\":\"31\",\"group\":\"Test\",\"licence\":null,\"created_at\":\"2017-04-22 05:18:19\",\"updated_at\":\"2017-04-22 05:18:19\",\"building\":{\"id\":2,\"name\":\"Fake Building\"}})"} 

I am aware that the second parameter in serializeData() is a EncodingParametersInterface object but I cannot find documentation on this nor can I tell how this is meant to be used by reading through the code.

[lindyhopchris]

Hello! You'll need to include the related resources. So you'll need to pass the encoder a set of encoding parameters, which with the include parameters as building and device-type.

The actual relationships in the JSON API spec don't include attributes of the related resources - as a relationship is a resource identifier, not the resource itself. That's why the included key contains a list of related resources that have been asked for.

[GregPeden]

Awesome, thanks!

For those who look this up later, the solution is as follows:

return Encoder::instance([
    Device::class => Devices\Schema::class,
    Building::class => Buildings\Schema::class,
    DeviceType::class => DeviceTypes\Schema::class
])->serializeData($this->device, new EncodingParameters(['building', 'device-type']));