Allow configuring multiple routes that point to different endpoints about laravel-graphiql HOT 4 CLOSED

I noticed this too; even my own projects based on rebing/graphql-laravel suffer this 😬

I was meant to look into for graphql-laravel but haven't found time yet.

from laravel-graphiql.

In order to make this happen, I think we would essentially need to switch the configuration from the current format into one that returns configurations for multiple routes.

-return ['route' => ['uri' => '/graphiql', ...], 'endpoint' => '/graphql', ...];
+return [
+    ['route' => ['uri' => '/graphiql/admin', ...]], 'endpoint' => '/graphql/admin', ...],
+    ['route' => [['uri' => '/graphiql/app', ...], 'endpoint' => '/graphql/app', ...],
+];

Then, the routes configuration file would need to iterate over those multiple routes and pass their config to the controller, which in turn passes the configuration values to the view.

I am not looking to implement this change myself. but am open to pull requests.

from laravel-graphiql.

I adapted our fork to support multiple schemas dynamically in the routes.php, this works for us 😄 :

/**
 * Get the schema from the request and append to the configured endpoints.
 */
if ($schema = Str::afterLast(trim(Request::capture()->getPathInfo(), '/'), '/')) {
    $schema = '/' . $schema;
    if ($config->get('graphiql.route.uri') != $schema) {
        $config->set('graphiql.route.uri', $config->get('graphiql.route.uri') . $schema);
        $config->set('graphiql.endpoint', $config->get('graphiql.endpoint') . $schema);
    }
}

from laravel-graphiql.

#11 gives a good idea of peoples expectations in this regard. Obviously, this package can't query random other packages config files.

I wonder what we could do here, i.e. have package A (graphql-laravel) provide package B (laravel-graphiql) the information automatically to generate the appropriate routes.

from laravel-graphiql.