save() on polymorphic relation don't work

Can we see your membership() relationship on the model?

Of course:

<?php namespace App;

use Illuminate\Auth\Authenticatable;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Auth\Passwords\CanResetPassword;
use Illuminate\Contracts\Auth\Authenticatable as AuthenticatableContract;
use Illuminate\Contracts\Auth\CanResetPassword as CanResetPasswordContract;


class User extends Model implements AuthenticatableContract, CanResetPasswordContract {

    use Authenticatable, CanResetPassword;

    /**
     * The database table used by the model.
     *
     * @var string
     */
    protected $table = 'users';

    /**
     * The attributes that are mass assignable.
     *
     * @var array
     */
    protected $fillable = ['name', 'email', 'password', 'membership_type', 'membership_id'];

    /**
     * The attributes excluded from the model's JSON form.
     *
     * @var array
     */
    protected $hidden = ['password', 'remember_token'];
    
    /**
     * Always hash the password
     *
     * @param $value
     */
    public function setPasswordAttribute ($value )
    {
        $this->attributes['password'] = bcrypt($value);
    }
    
    /**
     * Creates an polymorphic relationship for Lenicura, Employees, Customer and Partner
     *
     * @return \Illuminate\Database\Eloquent\Relations\MorphTo
     */
    public function membership ()
    {
        return $this->morphTo();
    }

}

<?php namespace App;

use Illuminate\Database\Eloquent\Model;

class Customer extends Model {

    protected $fillable = ['firstname', 'lastname'];

    public function user ()
    {
        $this->morphOne('App\User', 'membership');
    }

}

I don't think it's a relationship problem. But who knows ;)

@MichaelGrossklos There's no save on belongsTo and morphTo - these are child relations, so you need to have the parent saved, before you can create such relationship with associate. Like this:

$customer->save();
$user->membership()->associate($customer);

@JarekTkaczyk YOU MADE MY DAY!!

For all struggling with that, heres what I've changed:

Instead of using User::create() I do this:

 private function createUser ()
    {
        $user = new User;
        $user->name = $this->request->get('name');
        $user->email = $this->request->get('email');
        $user->password = $this->request->get('password');
        $user->save();

        return $user;
    }

And then simply follow @JarekTkaczyk suggestion:

 /**
     * Execute the command.
     *
     * @param \App\Http\Requests\CustomerRequest $customerRequest
     *
     * @return
     * @internal param \App\User $user
     */
    public function handle(CustomerRequest $customerRequest)
    {
        $customer = $this->dispatch(new CreateCustomerCommand($customerRequest));
        $user = $this->dispatch(new CreateUserCommand($this->userRequest));

        return $user->membership()->associate($customer);
    }

It works. Thx

@JarekTkaczyk Oh noooo! It doesn't work. The user and customer gets created. But the relationship isn't made. In my users table is no membership_type and membership_id in this particular user. As you can see here: http://f2w.me/_MySQL_5_6_19-1_exp1ubuntu2__Lenicura_homestead_users_1B0356FD.png

@MichaelGrossklos Well, I might have been not precise enough :)

associate doesn't update anything, it just sets the FK and the relation on the object. That said, after associating you still need to save the child model, a user in your case.

Ahhh ok. Makes sense ;) Thanks. Because of Behat problems I'm not in the situation to test it right now, but I will!

@JarekTkaczyk Nope, seems not be the case:

public function handle(CustomerRequest $customerRequest)
    {
        $customer = $this->dispatch(new CreateCustomerCommand($customerRequest));
        $user = $this->dispatch(new CreateUserCommand($this->userRequest));

        $user = $user->membership()->associate($customer);
        $user->save();

        return $user;
    }

User gets created but no relation.

@MichaelGrossklos And to make things clear - you expect membership_type and membership_id to be saved on the users table?

@JarekTkaczyk Sorry, found it. Was my foult. Was a problem with the controller. Anything is working like you suggested. But to answer your question: yes I do. Thanks again!