Closed TobiasFella closed 3 weeks ago
Yeah, pulling the Connection in there is a bit terrible. I did it this way because then we're already prepared for a future where access tokens change at runtime (refresh tokens, OIDC), but i guess we do need to push the token in there directly
The control point for tokens (ConnectionData::setToken()
) is already there anyway, and ConnectionData
can push the token down to NAM
, every time the token is updated. It can even store the token in NAM
, with ConnectionData::accessToken()
retrieving it from there (with tiny loss of efficiency vs. tiny win of memory).
right, that's nicer. I've updated the patch
Quality Gate failed
Failed conditions
C Reliability Rating on New Code (required ≥ A)
See analysis details on SonarCloud
Catch issues before they fail your Quality Gate with our IDE extension SonarLint