README

Implement feature-rich JSON:API compliant APIs in your Laravel applications using Doctrine ORM.

Overview

This package provides a comprehensive implementation of the JSON:API specification for Laravel applications using Doctrine ORM instead of Eloquent. It reduces boilerplate code by offering default controllers and actions that handle standard API operations while ensuring full compliance with the JSON:API standard.

Documentation

For detailed installation instructions, configuration guides and tutorials:

https://scholarshipowl.github.io/laravel-doctrine-jsonapi/

Features

• Complete JSON:API Implementation: Full compliance with the JSON:API specification
• Built for Doctrine ORM: Designed specifically for Laravel applications using Doctrine ORM
• Battle-tested: Production-ready and robust
• Standardised, Consistent APIs: Uniform interface for all resources
• Resource Operations:
  • Fetch resources with advanced querying
  • Fetch and manipulate relationships
  • Inclusion of related resources (compound documents)
  • Sparse field sets
  • Sorting
  • Pagination
  • Filtering
• Full CRUD Support:
  • Create resources
  • Update resources
  • Update relationships
  • Delete resources
• Authorization: Policy-based access control
• Auto-generated Documentation: Endpoints are automatically documented using Scribe

Bugs:

• In the WithUpdateRelationshipsTrait the we use UpdateToManyRelationshipsRequest for updating to-one relationships.
• Relationships with multipe resource type are not supported. Example is when we use inheritance type single table and we have different type for same table / relationship.

Roadmap

• Docs: Quickstart add how to install PHP section ( @see: php.new )
• Build documentation and testing for integration of Laravel Sanctum or Laravel Passport.
• Add Laravel Doctrine ACL package to testing
• Provide QueryBuilder for the filter parsers, instead of criteria as it allows to apply any types of filters.
• Remove the default request hydration from the package, as it may create security vulnerabilities. All the mutations should be handled by the application code, by the client.
• Improve security by adding ability checks on the transformer level when we try to include relationships.
• Scribe: Generated headers are not prperly defined, we got Accept: / everywhere.
• Allow override or provide ability for custom request authentication.
• Integrate scribe into the package. Automatically generate Open API specs.
  • Add documentation for scribe integration
  • Update metadata for each endpoint
    • Endpoint description
    • Endpoint tags
    • Endpoint name
    • Endpoint group
  • Route\URL params documentation
  • Query params documentation
    • Add a fields lists to each query documentation. Need to extract it from the transformer.
    • Filter query parameters documentation
  • Request body documentation
    • Analyze scribe default rules parser find ways to improve it.
  • Response body documentation
    • Create ValidationResponseAttribute that goint to read rules from validation and generate example response.
• Add documentation about the meta param usage. ( meta[account]=mailbox&meta[profile]=completeness )
• Make it possible to disable links generation. As it is not required by JSON:API spec and increases response size.
• Add generics to all the types using ResourceInterface
• Move default routes to the separate file and load them on boot. ( see how Scribe doing it )
• Create a validation rule "resource", "resourceExists" for validating resource identifier. Example of usage: php $this->validate($request, [ 'data' => 'required|resource:users', ]);
• Create default global error handler or write down documentation how to create such one. How to handle missing route\endpoint 404 and internal 500 errors.
• Checkout option for adding include params like "include=roles:sort" (TransformerAbstract.php:173)
• Integrate UUID support by default https://github.com/ramsey/uuid-doctrine

Next version

• Use PHP Attributes instead of ResourceInterface for the resource declaration.
• Metadata managment system similar to Doctrine one, that knows the resource schemas and relationships, etc. On boot register all the resources and cache them.
  • Resource type, transformers, relationships discovery, moved to the metadata system / ResourceManager.
  • Generate the resourceType depend on the entity name
  • Generate the transformers depend on the entity name and configuration path: app/Transformers/{Entity}Transformer.php
  • Allow defining relationships with PHP Attributes on the entity class.
  • The id get be retrieved using internal Doctrine functionality or just depend on public $id property.
• Migrate all the default users and roles to be UUID
• Improve transformer, make it handle relationships depend on resource. Use better name like "ResourceTransformer".

Support

If you encounter any issues or have questions, please report them using the GitHub Issues tracker.

License

This project is licensed under the MIT License - see the LICENSE file for details.