configureAuthClient effect now depends on [clearSession, refresh, user] instead of running every render; user tracks token presence, which the client publishes as session state.
Unmount cleanup stays a separate effect so re-registration does not briefly publish "no session" to subscribers.
Regression test: rerender does not re-register; unmount clears.
Checks: npm run verify.
Closes #95
- `configureAuthClient` effect now depends on `[clearSession, refresh, user]` instead of running every render; `user` tracks token presence, which the client publishes as session state.
- Unmount cleanup stays a separate effect so re-registration does not briefly publish "no session" to subscribers.
- Regression test: rerender does not re-register; unmount clears.
Checks: `npm run verify`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #95
configureAuthClienteffect now depends on[clearSession, refresh, user]instead of running every render;usertracks token presence, which the client publishes as session state.Checks:
npm run verify.c6f2f2eedcto19fe99695c