fresh_dio - Dio instance locked

[kuhnroyal]

In the lastest 0.3.0 null-safety release, the Dio client is locked from making requests before refreshing the token.

Sadly this also includes the token refresh request itself.
Also see: https://github.com/felangel/fresh/pull/39/files#r614289083

There is an open PR #45 which removes the locking.
In general I think it is a good idea to lock the instance but it should occur after the refresh request is sent and unlocked after the response is received and the token is stored.

As a workaround a new Dio instance can be constructed.

[rtviwe]

You can just call dio.unlock() inside your refreshToken callback

[rtviwe]

Also before migrating to dio 4.0.0 there was not any locking (see https://github.com/felangel/fresh/blob/f2470c98cb94a315ebbfbca7e3bc82aea18b0dc5/packages/fresh_dio/lib/src/fresh.dart)

[rtviwe]

There is also another bug which I fixed in PR with adding refreshed token to headers. For some reason, it disappeared after this commit b457b26

[felangel]

This should be fixed as part of #45 and included in v0.3.1 👍