Looking to hire Laravel developers? Try LaraJobs

laravel-resource-registry maintained by dandoetech

Description
Laravel bridge for DanDoeTech Resource Registry: ClassBasedDriver, capability interfaces, computed resolvers, ServiceProvider.
Author
Last update
2026/03/20 13:07 (dev-main)
License
Downloads
0

Comments
comments powered by Disqus

Laravel Resource Registry

Laravel bridge for the DanDoeTech Resource Registry. Auto-discovers Resource classes, binds the Registry as a singleton, and provides capability interfaces for Eloquent integration.

This is the central package — install it first, then add consumer packages as needed.

Installation

composer require dandoetech/laravel-resource-registry

The service provider is auto-discovered. Publish the config:

php artisan vendor:publish --tag=ddt-config

Quick Start

1. Define a Resource

Create a Resource class in app/Resources/:

<?php

declare(strict_types=1);

namespace App\Resources;

use DanDoeTech\ResourceRegistry\Resource;
use DanDoeTech\ResourceRegistry\Builder\ResourceBuilder;
use DanDoeTech\ResourceRegistry\Definition\FieldType;
use DanDoeTech\LaravelResourceRegistry\Contracts\HasEloquentModel;
use DanDoeTech\LaravelResourceRegistry\Contracts\HasPolicy;

class ProductResource extends Resource implements HasEloquentModel, HasPolicy
{
    public function model(): string { return \App\Models\Product::class; }
    public function policy(): string { return \App\Policies\ProductPolicy::class; }

    protected function define(ResourceBuilder $b): void
    {
        $b->key('product')
          ->label('Product')
          ->timestamps()
          ->field('name', FieldType::String, nullable: false, rules: ['required', 'max:120'])
          ->field('price', FieldType::Float, nullable: false, rules: ['required', 'numeric', 'min:0'])
          ->field('category_id', FieldType::Integer, nullable: false)
          ->belongsTo('category', foreignKey: 'category_id')
          ->hasMany('reviews')
          ->computed('category_name', FieldType::String, via: 'category.name')
          ->computed('orders_count', FieldType::Integer, via: 'count:orders')
          ->filterable(['name', 'price', 'category_id', 'category_name'])
          ->sortable(['name', 'price', 'created_at', 'orders_count'])
          ->searchable(['name'])
          ->action('create')
          ->action('update')
          ->action('delete');
    }
}

2. Use the Registry

The Registry is bound as a singleton. Inject or resolve it anywhere:

use DanDoeTech\ResourceRegistry\Registry\Registry;

$registry = app(Registry::class);

$product = $registry->getResource('product');
echo $product->getLabel(); // "Product"

foreach ($registry->all() as $resource) {
    echo $resource->getKey();
}

Resources are auto-discovered from configured paths on first access.

Configuration

config/ddt_registry.php:

return [
    // Directories scanned for Resource classes (relative to base_path)
    'resource_paths' => [
        'app/Resources',
        'Modules/*/Resources',
    ],
];

Note: The API route prefix is configured in config/ddt_api.php (from laravel-generic-api), not here. This config only controls resource discovery.

Glob patterns are supported — Modules/*/Resources discovers resources across all module directories.

Capability Interfaces

Framework-specific capabilities are opt-in via small interfaces. Implement only what you need:

// Link resource to an Eloquent model
interface HasEloquentModel
{
    /** @return class-string<Model> */
    public function model(): string;
}

// Link resource to a Laravel policy
interface HasPolicy
{
    /** @return class-string */
    public function policy(): string;
}

// Apply a query scope (e.g., user sees only own records)
interface HasScope
{
    /** @return class-string|Closure|null */
    public function scope(): string|Closure|null;
}

Bridge packages discover capabilities via instanceof:

$modelClass = $resource instanceof HasEloquentModel
    ? $resource->model()
    : throw new \RuntimeException("No model for '{$resource->getKey()}'");

Computed Field Resolvers

For resources with computed fields using via syntax, resolvers are built automatically:

Via syntax Resolver Example
relation.field RelationFieldResolver (subselect) category.name
count:relation RelationCountResolver (withCount) count:orders
pluck:relation.field RelationPluckResolver (GROUP_CONCAT) pluck:tags.name

For custom logic, implement EloquentComputedResolver:

use DanDoeTech\LaravelResourceRegistry\Contracts\EloquentComputedResolver;
use Illuminate\Database\Eloquent\Builder;

class CompletedOrdersCount implements EloquentComputedResolver
{
    public function apply(Builder $query): Builder
    {
        return $query->withCount(['orders as completed_orders' => fn ($q) =>
            $q->where('status', 'completed')
        ]);
    }

    public function filter(Builder $query, mixed $value, string $operator = '='): Builder
    {
        return $query->having('completed_orders', $operator, $value);
    }

    public function sort(Builder $query, string $direction): Builder
    {
        return $query->orderBy('completed_orders', $direction);
    }
}

Reference it in your resource:

->computed('completed_orders', FieldType::Integer, resolver: CompletedOrdersCount::class)

API Overview

Class Purpose
DdtServiceProvider Binds Registry singleton, publishes config
ClassBasedDriver Scans configured paths for Resource classes
PathResolver Resolves glob patterns to PHP file paths
HasEloquentModel Capability: link resource to Eloquent model
HasPolicy Capability: link resource to Laravel policy
HasScope Capability: apply query scope
EloquentComputedResolver Contract for custom computed field query logic
ViaResolverFactory Creates resolvers from via syntax strings

Testing

composer install
composer test        # PHPUnit (Orchestra Testbench)
composer qa          # cs:check + phpstan + test

License

MIT