Fix: Handle Null Username in API Response to Prevent Mapping Errors#13
Open
shubham-011bq wants to merge 7 commits intoLouisHDev:mainfrom
Open
Fix: Handle Null Username in API Response to Prevent Mapping Errors#13shubham-011bq wants to merge 7 commits intoLouisHDev:mainfrom
shubham-011bq wants to merge 7 commits intoLouisHDev:mainfrom
Conversation
added 7 commits
March 4, 2025 13:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 API response sometimes returns username as null, which causes issues in the data mapping process.
As a result, the loading state is incorrectly displayed on the dashboard/home screen.
This fix ensures that the app handles null values properly, preventing mapping errors and improving the user experience, by taking the user away from loading screen