[RFR] GraphQL providers enhancements

[djhi]

Following #2243

• Deprecate the override option
• Exports the buildQuery function in dialect packages
• Document how to wrap buildQuery to override specific queries

[Weakky]

I think the signature is wrong here: (buildQuery) => (introspectionResults) => (fetchType, resource, params).

Same goes for const builtQuery = buildQuery(introspectionResults)(fetchType, resource, params);

[djhi]

Right !

[djhi]

It seems cumbersome to use it that way, isn't it? Lot of boilerplate again...

What do you think of the following usage:

// in src/dataProvider.js
import buildGraphcoolProvider from 'ra-data-graphcool';

const buildQuery = (fetchType, resource, params, defaultBuildQuery) => {
    const builtQuery = defaultBuildQuery(fetchType, resource, params);

    if (resource === 'Command' && fetchType === 'GET_ONE') {
        return {
            // Use the default query variables and parseResponse
            ...builtQuery,
            // Override the query
            query: gql`
                query Command($id: ID!) {
                    data: Command(id: $id) {
                        id
                        reference
                        customer {
                            id
                            firstName
                            lastName
                        }
                    }
                }`,
        };
    }

    return builtQuery;
}

export default buildGraphcoolProvider({ buildQuery })

The dataProvider would call your buildQuery with the default one it uses.

EDIT: edited for even simpler usage

[djhi]

Actually a bad idea as one may need the introspection results for advanced scenarios

[Weakky]

Shouldn't it be builtQuery instead?

[djhi]

Good catch!

[fzaninotto]

I think we still use the override option in the dataProvider of the examples/graphcool-demo

[djhi]

Fixed the demo