Let morphMap Relation function to handle multiple classes for the same key

[giacomomasseron]

Hi,
I have 2 classes, parent and child, and I need that both have the same morph key.

What I can't do is:

Relation::morphMap([
      'key' => ParentClass::class,
      'key' => ChildClass::class,
]);

What I would like to do is:

Relation::morphMap([
      'key' => [ParentClass::class, ChildClass::class],
]);

[henzeb]

Why ? Is child a version 2 of parent?

[giacomomasseron]

Shouldn't all child classes be version 2 of the parent classes?
Otherwise why extend the parent class?

[henzeb]

Because the child can behave different than the parent class and the data might me different than it expected.

But that does not answer my question, why? And how to determine the correct class?

[giacomomasseron]

We are talking about morph key, it does not matter if the data between classes is different (and usually it is).

The idea is to leave me the choice to use it.
Potentially I might want to use the same morph key for all the models in my application.

[henzeb]

explain to me the use case then. I am trying to understand what you want to do.

[giacomomasseron]

Context:

• I am using Filament
• For project models, I use a proprietary package where I defined my models
• In the Filament project, every model defined in the package is extended

When in Filament I create a resource, I use the extended model (the Parent class).

Now, if I create a form for a morph relationship, Filament get info from database using the getMorphClass value of the parent class, when in the database the value is saved using the getMorphClass value of the child class (this value is added by another of my project).

I would need that parent and child classes share the same morph key.