Einar Gangsø

I'm not using the current factory system, so I'm very unlikely to be the one adding support for these.

Looks good to me

Could you rebase on laravel-doctrine/orm 1.8. Some of your commits (L9) was cherry-picked and thus have a new sha1. The original commits are now trying to be a part of...

@dpslwk Any thoughts? I know you tried to use illuminate/cache (which I would prefer, since it is most likely required by all who use this package), but there was some...

@seifane-wise When you rebase, drop the commits not from you. If using `git rebase -i upstream/1.8` can you replace `pick` with `drop` at the commits. Looks like at least three...

Which version of symfony/validator are you using?

How does your implementation of `Illuminate\Contracts\Routing::UrlRoutable` looks like? Seems like `resolveRouteBinding` would require the EntityManager? Might it be easier to just extend `Illuminate\Routing\UrlGenerator` and use `LaravelDoctrine\ORM\Contracts\UrlRoutable` in `UrlGenerator::formatParameters`. Seems to...

> should use `\Illuminate\Routing\Middleware\SubstituteBindings::class` I don't think you can, as laravel builds an instance of the model (entity) via the Container, which often is not possible whith doctrine entities. See...

@douma Yes, that works. Though it is a breaking change :/

Seems like a reasonable change, but this would probably break for everyone who have already created tables/columns with this name?