Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have added a
public
object to theSessionData
which still contains theUser
type like before.The
setUserSession
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