Guido Contreras Woda

@fritz-gerneth I don't follow: Why do you say a schema is used by the client only? I understand a schema as a contract, an agreement between the data provider (server)...

If you check apollo, they use GraphQL type language to define the schema, then js code to define implementations of messages: http://dev.apollodata.com/tools/graphql-tools/generate-schema.html Last step looks kind of like what I'm...

I'm not a fan of code generation tools, but I guess that's the easiest way of reusing your existing schema code. :+1:

I just stumbled upon the same problem. It seems it's still not fixed in v8.0.0

@ahjohannessen it has to do with how the `EsConnection` creates the `connection` actor. I'm not familiar with the classic actor implementation, so I wouldn't know how to conserve backwards compatibility....

@mitchellvanw let me know if there's anything I can do to help push this change forward!

@kirkbushell glad it helped! I had the intention of doing a more Laravelish metadata driver. Right now I'm using half of this package's objects and half of my own because...

It may be missing, yes.

@saintho All associations have a `getAssociation()` method that will expose Doctrine's `AssociationBuilder` object. You can always work around Fluent and go directly to Doctrine's php mapper, so this is not...

@patrickbrouwers the problem seems to be at this line: https://github.com/laravel-doctrine/orm/blob/1.1/src/Console/GenerateEntitiesCommand.php#L50 But ORM doesn't know it needs an ExtensibleClassMetadataFactory. We couldinject it on the command and let fluent override the injection...