Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feat: Build the User Profile Screen #83

Open
6 tasks
lkmandy opened this issue Feb 17, 2023 · 0 comments
Open
6 tasks

Feat: Build the User Profile Screen #83

lkmandy opened this issue Feb 17, 2023 · 0 comments
Assignees
@TikuGaelle
Labels
5 hours enhancement New feature or request feature a new feature

Comments

@lkmandy
Copy link
Contributor

lkmandy commented Feb 17, 2023

Description

Design and implement the user profile screen. We want users to be able to access their account details, settings, notifications, and payment methods. Users should also be able to edit these details whenever they wish.

Acceptance Criteria:

  • Users should be able to see their profile picture, name, and user name
  • Users should be able to edit their profile details
  • Users should be able to access their account, settings, notifications, and payment methods
  • Users should be able to log out from this screen
  • The current app version should be visible from this screen
  • Users should be able to access the app's terms and conditions

Screenshots/visuals

profile
@lkmandy lkmandy added enhancement New feature or request feature a new feature labels Feb 17, 2023
@fonkamloic fonkamloic added the 5 hours label Feb 17, 2023
@TikuGaelle TikuGaelle mentioned this issue Mar 1, 2023
Merged
16 tasks
fonkamloic added a commit that referenced this issue Mar 8, 2023
@fonkamloic
feat: user profile screen (#107)
3fbe1cb 
## Description
 User profile screen.
  Solves issue #83 

## Type of Change

<!--- Put an `x` in all the boxes that apply: -->

- [x] ✨ New feature (non-breaking change which adds functionality)
- [ ] 🛠️ Bug fix (non-breaking change which fixes an issue)
- [ ] ❌ Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] 🧹 Code refactor
- [ ] ✅ Build configuration change
- [ ] 📝 Documentation
- [ ] 🗑️ Chore


## Pre-launch Checklist

- [ ] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [ ] I read and ran all relevant commands as specififed in the Running
Tests section of the [Contributor Guide].
- [ ] The title of the PR follows the [Conventional Commits] guideline
- [ ] My local branch follows the naming standards in the [Deepsource
Branch Naming Convention] or [Biodiversity Branch Naming Convention]
- [ ] I listed at least one issue that this PR fixes in the description
above.
- [ ] I updated `pubspec.yaml` with an appropriate new version according
to the [pub versioning philosophy],
- [ ] I updated/added relevant documentation (doc comments with `///`).
- [ ] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [ ] All existing and new tests are passing.


[Contributor Guide]:
https://github.com/FlutterPlaza/.github/blob/main/CONTRIBUTING.md
[Conventional Commits]:
https://www.conventionalcommits.org/en/v1.0.0-beta.4/
[pub versioning philosophy]: https://dart.dev/tools/pub/versioning
[Biodiversity Branch Naming Convention]: https://bit.ly/3DyYSwM
[Deepsource Branch Naming Convention]: https://bit.ly/3Y08Gs4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TikuGaelle TikuGaelle

Labels
5 hours enhancement New feature or request feature a new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lkmandy @fonkamloic @TikuGaelle