Some usage issues about graphql-doctrine HOT 3 CLOSED

I strongly suggest to work with ChromeiQL (or equivalent) when writing queries to benefit from auto-completion.

1. Filtering with between, you missed the keys groups, from, and to:

query {
    Employee (sorting: { field: age, order: DESC }, filter: {groups: [{conditions: {
        age: {between: {from: 18, to: 55}}
    }}]}) {
        name
        age
    }
}

2. Yes you can do join, but only on relations known by Doctrine (assuming a Company entity exists):

query {
    Employee(filter: {groups: [{joins: {company: {conditions: [{name: {like: {value: "%foo%"}}}]}}}]}) {
        name
        age
    }
}

3. If you write a custom sort/filter by computing something, then you'll have to do some extra work to expose that computed value in your entity getter. You probably want to organize things to re-use the same code for both the getter and the custom sort/filter.

You may want to have a look in https://github.com/Ecodev/dilps/tree/master/server/Application/Api/Input. I don't think there is exactly what you need, but it's a real-world application using this lib.

Also I strongly suggest to browse the test data that cover a lot of common use-cases: https://github.com/Ecodev/graphql-doctrine/tree/master/tests/data/query-builder

from graphql-doctrine.

Oh, of course PR to improve the documentation are more than welcome. Some sections, such as filter and sorting, were written rather quickly. It would help to have an external point of view such as yours. Feel free to open a PR with your ideas as a starting point and it can then be improved together.

from graphql-doctrine.

Wow, thank you so much for your quick response. This would really help go in the right direction.

Sure, I am planning to this library more in our current application, I'm sure I would be able to contribute to the documentation soon once I have the more understanding of it.

Thank you so much once again!

from graphql-doctrine.