feat: programmatic discriminator mappings

[robertvansteen]

No description provided.

[joelwurtz]

Hey thanks for the initial work on this.

We made change to support this in #319 it will be available in next major version.

I'm closing this, but if you feel like the DX or other things does not work for this feature please let us know.

[robertvansteen]

Hey thanks for the initial work on this.

We made change to support this in #319 it will be available in next major version.

I'm closing this, but if you feel like the DX or other things does not work for this feature please let us know.

@joelwurtz thanks! Good to see this being added. The main reason for starting this work was that I ran into a challenge where the interface is in vendor so I won't be able to add any attribute on it. Do you see this being supported in some way?

[joelwurtz]

The main reason for starting this work was that I ran into a challenge where the interface is in vendor

Both source and target are in vendor ?
But yes this a global problem if source is in vendor and target is an array (or also in vendor) or the reverse situation.

For that we are open to a more global feature that allow defining mapper configuration without any attribute. The main work for this would be on the DX (how the developer will interact with this configuration). I'm open to do the work if there is a nice proposition.