Added isLoggedIn property to get current user object fetched from getCurrentUser method #214
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.
Summary
Currently, the getCurrentUser method returns an object with only the userId property, but it would be useful to also include the isLoggedIn property to determine the login status of the current user.
Current behavior:
getCurrentUser()
only returns an object with the userId property:{ userId: "1" }
Expected behavior:
getCurrentUser()
should return an object with bothuserId
andisLoggedIn
properties, where isLoggedIn is a boolean indicating whether the user is logged in or not:{ userId: "1", isLoggedIn: true }
Changes Done:
Modified the getCurrentUser method to return the isLoggedIn property along with userId. This will provide more comprehensive information about the current user and their session status.
Additional context:
This update would allow users or developers to directly access the login status of the current user without needing to perform a separate check.
Testing Plan
This can be tested by calling the
getCurrentUser
Method and verifying the current user response object,Master Issue
Closes #213