Omar Herri

Did someone managed to resolve this guys ??

@vinicius73 this doesn't need any testing cause i just added Macroable trait and there is no conflit with methods name.

This would be useful in way that we don't have to duplicate the same code every where. This only add compatibility with Laravel macro.

I think you can achieve this easily with this command: `$builder->__toString();`

No i tested this. it shows the current query generated by your builder. Just give it a try.

I see because you are using QueryBuilder. This is an example i'm using right now: ``` $gql = (new Query('page')) ->setArguments(['where' => new RawObject('{id: "'.$id.'"}')]) ->setSelectionSet( [ 'title', 'publishedAt', 'updatedAt',...

I followed you principales and i feel more confortable now about the outcome. So to tackle the dependency between the packages i created one package which contains all the contracts...

#51

> Did you ever figure this out? Running into a similar issue. It works when you use create or update but not with save.