optionally make useDirectusUser() silent

[sandros94]

Currently using useDirectusUser to check not only its data but to check if it is logged in at all to handle some logic.

<script setup>
const user = useDirectusUser()
</script>

The inconvenient is that while a non-logged user is navigating the console gets filled (correctly) with 401 Unauthorized errors.

Could there be a way to make it silent so that it keeps this functionality but doesn't spam the console? Or am I doing it wrongly?

[sandros94]

Oh, this might be due to something else.

Basically, if I'm not wrong, is that since useDirectusUser is based off the useState and it is not retaining it between dev restarts, it keeps the refresh tokens, but directus.user being empty it is not able to convalidate it?

[sandros94]

Mmmh... probably I'm off track. Otherwise this should have worked:

<script setup>
// check if user is logged in
const { fetchUser, setUser } = useDirectusAuth()
const user = useDirectusUser()

// on cold load/refresh, check if user has a valid session via cookies
if (!user.value) {
  const user = await fetchUser()
  setUser(user.value)
}
</script>

[sandros94]

What I'm trying to solve is the spam of the following for non-logged users:

GET https://my-directus-domain.example/users/me 401
[Directus Error]: FetchError:  (401  (https://my-directus-domain.example/users/me))
Couldn't fetch user Error

[sandros94]

Mmmh... probably I'm off track. Otherwise this should have worked:

<script setup>
// check if user is logged in
const { fetchUser, setUser } = useDirectusAuth()
const user = useDirectusUser()

// on cold load/refresh, check if user has a valid session via cookies
if (!user.value) {
  const user = await fetchUser()
  setUser(user.value)
}
</script>

still, if I login and then logout the spam stops, so it must be something about the old cookies and the new state session (both in dev and pre-production)