for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
namespace Spatie\LaravelEndpointResources;
use Illuminate\Support\Arr;
trait HasEndpoints
{
/** @var bool */
protected $mergeGlobalEndpoints = false;
public function endpoints(string $controller = null, $parameters = null): EndpointResource
$endPointResourceType = $this->mergeGlobalEndpoints
? EndpointResourceType::MULTI
: EndpointResourceType::LOCAL;
$endPointResource = new EndpointResource($this->resource, $endPointResourceType);
resource
In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:
class MyClass { } $x = new MyClass(); $x->foo = true;
Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:
class MyClass { public $foo; } $x = new MyClass(); $x->foo = true;
if ($controller !== null) {
$endPointResource->addController($controller, Arr::wrap($parameters));
}
return $endPointResource;
public static function globalEndpoints(string $controller = null, $parameters = null): EndpointResource
$endPointResource = new EndpointResource(null, EndpointResourceType::GLOBAL);
public static function meta()
return [];
public function mergeGlobalEndpoints()
$this->mergeGlobalEndpoints = true;
return $this;
public static function collection($resource)
return parent::collection($resource)->additional([
'meta' => self::meta(),
]);
public static function make(...$parameters)
return parent::make(...$parameters)->mergeGlobalEndpoints();
spatie /
laravel-resource-links
In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:
Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: