[Feature] Relations columns(properties) view as additional panels/subviews(hasMany and belongTo) in show action

[izica]

I have been looking for a solution for a while, but I still can not find it.
Had to implement it at my project.

Model relations:

    public function account_legal_entity()
    {
        return $this->belongsTo('App\Models\AccountLegalEntity');
    }

    public function account_sms_codes()
    {
        return $this->hasMany('App\Models\AccountSmsCode');
    }

Controller:

    protected function setupShowOperation()
    {
        $this->crud->setValidation(AccountRequest::class);

        $this->crud->addColumn([
            'name'            => 'account_sms_codes',
            'label'           => 'Sms codes',
            'type'            => 'relation_has_many',
            // url piece for CRUD actions
            'backpack_entity' => 'accountsmscode',
            // set model to get from fillable
            'model'           => \App\Models\AccountSmsCode::class,
            //or set columns
            'columns'         => [
                'sms_code'   => 'Code',
                'expired_at' => 'Expired date',
            ],
        ]);

        $this->crud->addColumn([
            'name'            => 'account_legal_entity',
            'label'           => 'Legal entity',
            'type'            => 'relation_belongs_to',
            // url piece for CRUD actions
            'backpack_entity' => 'accountlegalentity',
            //optional, get from fillable by default
            'columns'         => [
                'name'   => 'Company name',
                'owner_firstname' => 'Owner firstname',
            ],
        ]);
    }

[welcome[bot]]

Hello there! Thanks for opening your first issue on this repo!

Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.

Backpack communication channels:

• Bug Reports, Feature Requests - Github Issues (here);
• Quick help (How do I do X) - Gitter Chatroom;
• Long questions (I have done X and Y and it won't do Z wtf) - Stackoverflow, using the backpack-for-laravel tag;
• Showing off something you've made, asking for opinion on Backpack/Laravel matters - Reddit;

Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.

Thank you!

--
Justin Case
The Backpack Robot

[tabacitu]

That's really cool @izica . We were talking about going for something like that in 4.1.x - but in my mind it worked better as a Widget.

Any particular reason why you built it as a column instead of a Widget? I may be missing something, but at first glance I think what you have there needs quite a few workarounds in the HTML (close table, output stand-alone column, begin table). Coding it as a widget would not need that, since you can push widgets in particular sections/stacks.

[izica]

@tabacitu Hello, my team was thinking about the Widget option, but we decided that this method is better for us (define it as a regular column).
We decided to offer this to the community.

[tabacitu]

Please do! A PR is very much appreciated - hell, even a copy-paste is better than starting from scratch 😆

[linear5ky]

Hi,
Thanks for this. It was something I was planning to incorporate in a new project. So if you could share the column code that would be appreciated :)

[izica]

@tabacitu need some refactoring before PR. it can take few days.
think need to rename types with prefix "panel_" to avoid future intersections with common fields
panel_relation_has_many
panel_relation_belongs_to

any ideas about field
'backpack_entity' => 'accountsmscode',
these fields are used to interact with crud actions, maybe there is a more elegant way to get this?

[tabacitu]

@izica no rush on our end. We won't be able to take a look at this until we launch 4.1

think need to rename types with prefix "panel_" to avoid future intersections with common fields
panel_relation_has_many
panel_relation_belongs_to

That's one reason why I thought it would be easier to implement as a Widget 😄

any ideas about field
'backpack_entity' => 'accountsmscode',
these fields are used to interact with crud actions, maybe there is a more elegant way to get this?

I don't understand this - could you please rephrase?

[enefeka]

Hi, that looks really cool! Adding to @linear5ky comment, could you please share that code? Thanks!

[izica]

@tabacitu @linear5ky @enefeka
Laravel-Backpack/CRUD#2752

[enefeka]

Awesome, thanks!

[linear5ky]

Great work. Thank you for sharing!

[jcastroa87]

Hello.

Since this great feature became a plugin, we will close this discussion.

Thanks to @izica

Cheers