document sessionClaims property for useAuth

[ijxy]

⚠️ Requires clerk/javascript#4823 to be merged

Explanation:

This PR:

This documents the sessionClaims property for the various implementations of useAuth as added in clerk/javascript#4823 and which https://clerk.com/docs/backend-requests/making/custom-session-token#use-the-custom-claims-in-your-application actually claims is already available

Checklist

• I have clicked on "Files changed" and performed a thorough self-review
• I have added the "deploy-preview" label and added the preview link(s) to this PR description
• All existing checks pass

[alexisintech]

Requires clerk/javascript#4823 to be merged

Side note: I'm not sure if this will actually get merged - it was my mistake to say that you can access the Auth object using useAuth() - it's not true. you can access the Auth object server-side, and if you need some of those properties client-side, you can use the useAuth() hook but not all properties will be available, such as sessionClaims.
I made this fix in this PR: #1836
For example, you can see the specific diff here: https://github.com/clerk/clerk-docs/pull/1836/files#diff-32a8aa53d6ed186d319a0345942cd6e8ecc0600e08948fd37f10de0d8b7ab135R8

[ijxy]

Hi @alexisintech, thanks for your feedback!

I appreciate that it not an easy job keeping documentation up to date, especially when the terminology is so overloaded.

Technically, you can already access the sessionClaims on the client, using the useSession hook (see below). Regardless of whether my proposed change to make them accessible from useAuth are accepted, perhaps this is worth mentioning too. Something for you to decide!

// has the type `JWTClaims` instead of `JWTPayload` (which is the type that inherits the
// custom session claims), but does actually contain the custom claims
useSession().session?.lastActiveToken?.jwt?.claims