I have added a public object to the SessionData which still contains the User type like before.
The setUserSession and replaceUserSession have the parameters as described in #47
The SessionData type is no longer exposed in favor of PublicSessionData and PrivateSessionData.
(only used internally from now on)
I'm not really sure about this solution yet.
What I'm thinking is to let go of the user property as a session check and instead just use public like user is used right now. There won't be a built in computed user but this can easily be added by wrapping the useUserSession:
This way you don't have to use user and can add anything you want (as long as there is something)
Problem is.. useUserSession is already taken as composable name
I have added a
public
object to theSessionData
which still contains theUser
type like before. ThesetUserSession
andreplaceUserSession
have the parameters as described in #47The
SessionData
type is no longer exposed in favor ofPublicSessionData
andPrivateSessionData
. (only used internally from now on)I'm not really sure about this solution yet. What I'm thinking is to let go of the
user
property as a session check and instead just usepublic
likeuser
is used right now. There won't be a built in computeduser
but this can easily be added by wrapping theuseUserSession
:This way you don't have to use
user
and can add anything you want (as long as there is something) Problem is..useUserSession
is already taken as composable name