code16/sharp
Code-driven CMS framework for Laravel (PHP 8.3+/Laravel 11+). Build admin/CMS sections with a clean UI and strong DX: CRUD with validation, search/sort/filter, bulk or custom commands, and authorization—no front-end code required, data-agnostic.
Entity states are a bit of sugar to easily propose a state management on entities. It could be a simple "draft / publish" state for a page, or something more advanced with many states for an order for instance.
php artisan sharp:make:entity-state <class_name> [--model=<model_name>]
First, you'll have to write a class that extends the Code16\Sharp\EntityList\Commands\EntityState abstract class.
You'll have to implement two functions: buildStates() and updateState($instanceId, $stateId).
The goal is to declare the available states for the entity, using $this->addState():
class ProductState extends EntityState
{
protected function buildStates()
{
$this->addState('active', 'Active', 'green')
->addState('inactive', 'Retired', 'orange')
->addState('coming', 'Coming soon', '#ddd');
}
// ...
}
$this->addState() takes 3 parameters:
For the color, you may indicate anything that the browser would understand (an HTML color name or a hexadecimal value).
When the user clicks on a state to update it, the updateState() method is called.
class ProductState extends EntityState
{
public function updateState($instanceId, $stateId): array
{
Product::findOrFail($instanceId)
->update(['state' => $stateId]);
return $this->refresh($instanceId);
}
// ...
}
About the return $this->refresh($instanceId);: Entity states can return either a refresh or a reload (as described in the Commands documentation), but if omitted the refresh of the $instanceId is the default (meaning in the code sample above this line can be removed).
Once the Entity state class is defined, we have to add it in the Entity List or in the Show Page config:
class ProductList extends SharpEntityList
{
function buildListConfig(): void
{
$this->configureEntityState('state', ProductState::class)
}
// ...
}
The first parameter is a key which should be the name of the attribute.
The state will be displayed in the top section of the Show Page (if you have one).
In the Entity List, it will be displayed in a new column at the end of the list, unless you have declared a specific column (in this case, you can choose where to place it):
class ProductList extends SharpEntityList
{
protected function buildList(EntityListFieldsContainer $fields): void
{
$fields
->addField(EntityListField::make('title')->setLabel('Title'))
->addField(EntityListStateField::make()->setLabel('State'))
->addField(/* ... */);
}
// ...
}
Entity states can declare an authorization check very much like Instance Commands:
class ProductState extends EntityState
{
public function authorizeFor($instanceId): bool
{
return Product::findOrFail($instanceId)->owner_id == auth()->id();
}
// ...
}
How can I help you explore Laravel packages today?