# Building a Show Page

Between an Entity List and a Form, you might want to add a Show page to display a whole instance, and allow the user to interact with it through Commands.

Note that building a Show Page is really optional; but in some situations it could be really helpful to add this layer — and it can be even a must-have when dealing with "single" resources, such as a personal account, or a configuration entity, for which it's weird to build an Entity List.

# Generator

php artisan sharp:make:show-page <class_name> [--model=<model_name>]

# Write the class

First we build a class dedicated to our Show Page extending Code16\Sharp\Show\SharpShow; and we'll have to implement:

  • buildShowFields(FieldsContainer $showFields) and buildShowLayout(ShowLayout $showLayout) to declare the fields presenting the instance.

  • find($id): array to retrieve the instance.

  • buildShowConfig() (optional).

In detail:

# buildShowFields(FieldsContainer $showFields): void

Very much like Form's buildFormFields(), this method is meant to host the code responsible for the declaration and configuration of each show field. This must be done by calling $showFields->addField:

function buildShowFields(FieldsContainer $showFields): void
{
    $showFields
        ->addField(
            SharpShowTextField::make("name")
                ->setLabel("Name")
        )
        ->addField(
            SharpShowPictureField::make("picture")
        );
}

# Common attributes to all show fields

Each available Show field is detailed below; here are the attributes they all share:

  • setShowIfEmpty(bool $show = true): self: by default, an empty field (meaning: with null or empty data) is not displayed at all in the Show UI. You can change this behaviour with this attribute.

# Available simple Show fields

# Embedding an Entity List in a Show

A crucial feature in the ability given to add a full Entity List in a Show, to display and interact with some "one to many" related data.

Let's see a simple example: we want to display the pilots list dedicated to a spaceship. In the spaceship Show page, we can add a pilots Entity List as a field:

function buildShowFields(FieldsContainer $showFields): void
{
    SharpShowEntityListField::make("pilots", "pilot");
}

Sharp will consider this as a regular Entity List, meaning it will look for a sharp.entities.pilot.list config key containing an EntityList class name, build it and display it the Show as a field (see below for layout), with the full feature set of an Entity List: filters, commands, reorder, entity state, search...

Clicking a row in the EntityList can lead to whatever you've configured for this entity: a Show Page or a Form. Sharp will maintain a navigation breadcrumb under the hood to, in this case, get back to the spaceship Show after a pilot update.

Notice that you have three possibilities for the actual code of this EntityList:

  • if you want to have a "pilots" entity in the main menu, you can reuse the same EntityList instance for the Show Page ( and configure it to scope the data, as we'll discuss below),

  • or you can build a specific EntityList without declaring it in the main menu,

  • or you can have both, making the spaceship Show version of the pilots EntityList extend the other.

As always with Sharp, implementation is up to you.

But at this stage we still have a major issue: how to scope the data of the EntityList? In our case, we want to display and interact only with pilots linked to our spaceship... For this and more on personalization, refer to the detailed documentation of this field:

# buildShowLayout(ShowLayout $showLayout): void

The show layout is a simplified version of the Form layout, and is made of sections which contains columns of fields .

# Sections

A section is just a block of fields, packed in columns:

function buildShowLayout(ShowLayout $showLayout): void
{
    $showLayout->addSection(
        'Description', 
        function(ShowLayoutSection $section) {
            ...
        }
    );
}

A section can be declared collapsable:

function buildShowLayout(ShowLayout $showLayout): void
{
    $showLayout->addSection(
        'Description', 
        function(ShowLayoutSection $section) {
            $section->setCollapsable();
        }
    );
}

# Columns and fields

Just like for Forms, a ShowLayoutSection is made of columns and fields. So completing the example above:

function buildShowLayout(ShowLayout $showLayout): void
{
    $showLayout->addSection(
        'Description', 
        function(ShowLayoutSection $section) {
            $section->addColumn(
                9, 
                function(ShowLayoutColumn $column) {
                    $column->withSingleField("description");
                }
            );
        }
    );
}

A ShowLayoutColumn, very much like a FormLayoutColumn, can declare single field rows and multi fields rows. Report to the Form layout documentation to find out how.

# SharpShowListField's layout

Like SharpFormListField in Forms, a SharpShowListField must declare its item layout, in order to describe how fields are displayed, like in this example:

function(ShowLayoutSection $section) {
    $section->addColumn(9, 
        function(ShowLayoutColumn $column) {
             $column->withSingleField("pictures", function(ShowLayoutColumn $listItem) {
                  // Notice that the list item layout is just a ShowLayoutColumn
                  $listItem
                      ->withSingleField("file")
                      ->withSingleField("legend");
             });
        }
    );
}

# Embedded Entity Lists

An embedded Entity List in treated as a special section; its label will be displayed as section title.

function buildShowLayout(ShowLayout $showLayout): void
{
    $showLayout->addEntityListSection('members');
}

Like regular sections, embedded Entity List can be declared collapsable.

# find($id): array

As for Forms, the method must return a key-value array:

function find($id): array
{
    return [
        "name" => "USS Enterprise",
        "capacity" => 3000
    ];
}

And as for Forms, you'll want to transform your data before sending it.

function find($id): array
{
	return $this
		->setCustomTransformer(
		    "name", 
		    function($value, $spaceship) {
			    return strtoupper($spaceship->name);
		    }
		)
		->setCustomTransformer(
		    "picture", 
		    new SharpUploadModelThumbnailUrlTransformer(600)
		);
}

Transformers are explained in the detailed How to transform data documentation.

# buildShowConfig(): void

Very much like EntityLists, a Show can declare a config with EntityState handler, or Breadcrumb configuration:

function buildShowConfig()
{
   $this
        ->configureBreadcrumbCustomLabelAttribute("name")
        ->configureEntityState("state", SpaceshipEntityState::class);
}

Here is the full list of available methods:

  • configureBreadcrumbCustomLabelAttribute(string $breadcrumbAttribute): declare the data attribute to use for the breadcrumb; see detailed doc
  • configurePageAlert(string $template, string $alertLevel = null, string $fieldKey = null, bool $declareTemplateAsPath = false): display a dynamic message above the Show Page; see detailed doc
  • configureEntityState(string $stateAttribute, $stateHandlerOrClassName): add a state toggle, see detailed doc

# Accessing the navigation breadcrumb

A common pattern for Shows is to add an embedded EntityList with related entities, and to allow update but also creation from there. Taking back our spaceship / pilots example, we may need to add a pilot to the spaceship. Question is: how can we attach a newly created pilot to a spaceship?

Answer is: accessing the navigation breadcrumb, with Sharp Context, and more precisely with its getPreviousPageFromBreadcrumb() method. Here's a full example:

class PilotSharpForm extends SharpForm
{
    use WithSharpFormEloquentUpdater, WithSharpContext;

    [...]

    function update($id, array $data)
    {
        $pilot = $id ? Pilot::findOrFail($id) : new Pilot;
        $pilot = $this->save($pilot, $data);
        
        if(currentSharpRequest()->isCreation()) {
            if($breadcrumbItem = currentSharpRequest()->getPreviousShowFromBreadcrumbItems("spaceship")) {
                Spaceship::findOrFail($breadcrumbItem->instanceId())
                    ->pilots()
                    ->attach($pilot->id);
            }
        }
    }
}