feat: Add user profile editing interface.#1073
Open
Shanukeshri wants to merge 1 commit into
Open
Conversation
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
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.
Related Issue
Closes #1068
Summary
Adds a user profile editing interface, allowing users to access and modify profile information through a dedicated Profile Settings section.
Changes Made
Testing
Screenshots
Before
After
Checklist
Notes
While implementing this feature, I observed that a complete profile management system would require additional backend and database support, including persistent storage of profile information, validation, profile image handling, and corresponding API endpoints.
Since Issue #1068 primarily focuses on the absence of a profile editing interface, this PR is intentionally limited to the frontend UI and local state management. The additional backend functionality is outside the scope of this contribution and may be addressed in a separate issue or follow-up PR.