Problem using along with CASL about graphql

[eddyystop]

The service calls made by resolves are no different than any other service calls made by the service.

Perhaps you can ask in #general how to set headers for such calls.

[vigalo]

Thanks for your quick response .
The service calls are a little different. Looking at sources I found :

Enabled Feathers authentication on services for services called in

GraphQL resolver functions.

Combined changes for graphql and generator-feathers-plus

• Summary:

• params.provider, user & authenticated are copied from the
  graphql service call into the params for every Feathers service call
  in a resolver of BatchLoader.

• If you need additional props to be copied over, include their names in
  options.extraAuthProps and convertArgsToFeathers.

• For custom resolvers or BatchLoaders, you need to record the
  convertArgsToFeathers() call as explained in the details.

• Note you can enable authentication on a Feathers service or graphql
  only if you've run generate authentication first.

• Details:

• 'content' param in resolver calls now contains
  provider: params.provider, user: params.user &
  authenticated: params.authenticated (if any) from the /graphql call.

• In const createdService = createService(options);
  options.extraAuthProps can pass an array of additional prop names
  to be copied from params to content.
  This allows other auth-related props to be copied into content.

• The previous convertArgsToFeathers(args, ast, {...}) is recoded to
  const convertArgs = convertArgsToFeathers([/* prop names */]);
...
convertArgs(args, content, ast, {...})
  where the pop names would normally be the same names used in
  options.extraAuthProps. These are additional props to copy into parms
  for the Feathers service call being made in the resolver function.

So, my workaround to solve my problem was;
In graphql.service.?s :

  // !code: func_init // !end
  let options = {
    schemas,
    resolvers,
    extraAuthProps: ['headers']
  };
  // !code: func_options // !end

In service.resolvers.?s :

  // !code: extra_auth_props
  const convertArgs = convertArgsToFeathers(['headers']);
  // !end

from graphql.

[eddyystop]

Info thanks. I assume your server does not have websicket clients.

The generated code is meant to be changed for particular circumstances like yours.

[vigalo]

Thanks, eddystop :

Yes, my server has websockets clients althought currently I'm implementing the graphql and trying it with GraphiQl over rest for now.

[eddyystop]

I think I can close this since the elapsed time would indicate the issue is resolved.