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.
Requirements
For changes to apps
If applicable
Summary
This is an larger change than I had intended, but the point is to unify the ways we are using the session and user objects in core. While I've collapsed a couple of interfaces, these are not (as far as I can see) used outside of the framework itself, so this is technically not a breaking change.
I've also renamed
useSessionUser
touseSession
as this more accurately reflects what it returns (the user data is a property of the session), but for backwards compatibility, I kept theuseSessionUser
alias around. At a later point, we might want to change things souseSession
returns the session anduseSessionUser
just returns the user.Screenshots
Related Issue
Other