Setup of graphql_flutter post app initialisation and refreshing of tokens

[Aeseir]

Hi all,

Current usage pattern of wrapping graphql_flutter around MaterialApp doesn't make sense to me, as there is a unsecured component and a secured component, additionally our background service periodically refreshes token to ensure seamless transaction for user, which is not clear on how we integrate with graphql_flutter.
Ensuring configuration of auth link before user even hits the secured spaces doesn't logically work (and it risks pushing away potential new users that we are trying to convert).

Scenario for us is:

1. Launch app
2. User consumes public services
3. User wants to execute an admin/paid function they get redirected to sign in or sing up page
4. Upon login user consumes admin/paid function that calls our graphql api endpoint
5. Upon token expiration background service triggers token update

Config documentation indicates that authlink setup should take place at point 1, which is illogical at this point.
Ideally we want it done somewhere between 3-4 so that access token is captured and can be consumed, as well as after step 5 when we get updated token.

Currently looking at graph client as alternative option but before i go down that path, i want to know whether graphql_flutter can handle this scenario before i move onto another solution.