fix: narrowed session type passed to fetch
session hook
#71
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.
The return value of
requireUserSession
is guaranteed to have theuser
component defined.Previously, the return type was changed to reflect that fact but the session type passed to the
fetch
hook was not.(It was not immediately clear to me, but the result of
requireUserSession
is passed into thefetch
hook)This fixes that and should avoid users to do an unnecessary check when hooking into
fetch
Previously:
With this PR:
Also,
ActiveUserSession
is not exposed because the type is completely defined byUserSession
andUser
.