Closed rabol closed 3 years ago
Hi, what pages do you think the description should be on? Only on the list or everywhere?
I think it should be available on all screens / operations. maybe a resouce::description() that would be used the same way as the resource::label() in the constructor
Hey, @rabol I have added a new method:
/**
* Get the descriptions for the screen.
*
* @return null|string
*/
public static function description(): ?string
{
return null;
}
Then it will look like this:
On a Screen, there is the name and description property that is displayed as a header. When using a CRUD / Resource there is no possibility to set the description of the Screen.
The name property of the Screen is taken from the resource::label() in the constructor