Accesssing apolloClient inside boot file? about app-extension-apollo HOT 2 CLOSED

Hi @Quasarman

If you want to manipulate the apollo client or provider (after their creation) or their configs (before their creation), you can do so using the provided hooks. If that is not enough, you can unregister the extension by removing it from quasar.extensions.json and registering its boot file manually in quasar.conf.js in the order you need it in.

quasar.extensions.json

{
...
-  "@quasar/apollo": {
-    "graphql_uri": "https://example.com/graphql"
-  }
...
}

quasar.conf.js

-module.exports = function (/* ctx */) {
+module.exports = function (ctx) {
...
     boot: [
+      '~@quasar/quasar-app-extension-apollo/src/boot/' + (ctx.mode.ssr ? 'apollo-ssr' : 'apollo'),
       'my-other-boot-file-that-should-run-after-apollo'
     ],
...
     build: {
      env: {
          ...
+        GRAPHQL_URI: process.env.GRAPHQL_URI // to allow overriding the uri with `GRAPHQL_URI=https://example.com/graphql quasar dev`
      },

(Take a look at https://github.com/quasarframework/app-extension-apollo/blob/182654829e90ef4e2d8ab43f3c96c3edb0d7adf6/src/index.js lines 8 and 15)

Now you can access apolloProvider in your boot file:

  console.log(app.apolloProvider.defaultClient.version)

To explain why the extension boot file is run last, we used conf.boot.push which pushes the boot file to the end of the boot files array (may be not the best choice 😄 ).

from app-extension-apollo.

Hello @ejez

Thanks for the detailed explantation this helps alot!

from app-extension-apollo.