laravel icon indicating copy to clipboard operation
laravel copied to clipboard

JSON:API for Laravel applications

Results 83 laravel issues
Sort by recently updated
recently updated
newest added

Hi, I'm fallowing the documentation about attribute hydration and found out that either there is a bug (the method does not exist) or the documentation is wrong. In [docs](https://laraveljsonapi.io/docs/2.0/schemas/attributes.html#attribute-hydration) there...

documentation

Hey @lindyhopchris, appreciate all your hard work on this (and the previous version as well). Was curious if the atomic operations extension to the spec (https://jsonapi.org/ext/atomic/) is on the radar...

Hi all I'm wanting to change some functionality within a project that we're working on to better fit with the opinions that we as a team have with regards to...

I'm unsure if the feature I'm describing here is not implemented, or if I am just not configuring things correctly to make it work this way. If I have a...

enhancement

It is possible? For now, when i create a resource, related model is saved, but related columns in main resource is not filled at all. My guess is that the...

bug

There's nothing in the fields chapter of the docs about how to write your own fields. This probably needs documenting. Raised because someone asked on Slack about supporting spatial fields;...

documentation

Is it possible to add a link to a relationship? So add a link to the `firstQuestion` ```json "relationships": { "questions": { "links": { "firstQuestion": "http://localhost/api/v1/questions/616c98f8-3ea9-4bb2-8152-3dd40c3846eb", "related": "http://localhost/api/v1/surveys/4b732db9-48da-43c9-bec0-6df2dc7dcbe3/questions", "self": "http://localhost/api/v1/surveys/4b732db9-48da-43c9-bec0-6df2dc7dcbe3/relationships/questions"...

As per this clarification to the spec: https://github.com/json-api/json-api/pull/1604 Need to ensure that all our response documents have a top-level `self` link that would allow a client to refresh the document...

Sparse fieldset requests don't seem to be working with included relationships... `/api/v1/images?include=places&fields[places]=name,slug` returns all attributes for places, instead of just `name` and `slug`, as [JSON:API specifies here](https://jsonapi.org/format/#fetching-sparse-fieldsets).

needs reproduction

Hello, I've noticed that in 3 issues as well as the documentation: https://laraveljsonapi.io/docs/1.0/requests/authorization.html#relationship-authorization It's mentioned that it's possible to do field-level authorization by writing ones own authorizer. Can someone please...