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.

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

Dynamic Role-Based Dashboard and Wallet Connection #40

Open
gchyuli opened this issue Feb 24, 2025 · 3 comments · May be fixed by #41
Open

Dynamic Role-Based Dashboard and Wallet Connection #40

gchyuli opened this issue Feb 24, 2025 · 3 comments · May be fixed by #41
Assignees
Labels

Comments

@gchyuli
Copy link
Collaborator

gchyuli commented Feb 24, 2025

Description 📺

Current:

  • There is a "Clear Role" button on the home page, initially designed to ensure the dashboard updates dynamically based on the selected role (lender or borrower).
  • When users attempt to connect their wallet, they are prompted to select a role, but this process does not dynamically update the dashboard as expected.

New Design:

  • Remove the "Clear Role" button.
  • Implement a dynamic dashboard that updates automatically when the user selects their role during the wallet connection process.

Proposed Actions 🤨

Fork and Create Branch:

git checkout -b feature-dynamic-role-dashboard-[issue-number]

Implement Changes:

UI/UX Updates:

  • Remove the "Clear Role" button from the home page.
  • When the user selects a role while connecting their wallet, automatically redirect them to the appropriate dashboard (Lender Dashboard or Borrower Dashboard).
  • Ensure that the dashboard updates dynamically based on the selected role.

State Management Enhancements:

  • Store the selected role persistently after wallet connection.
  • Ensure the selected role is reflected throughout the app.

Testing:

  • Verify that the correct dashboard is displayed immediately after wallet connection.
  • Ensure there are no broken states due to removing the "Clear Role" button.

Run Tests and Commit Changes:

Write unit and integration tests to verify:

  • The "Clear Role" button is removed.
  • The dashboard updates dynamically when the wallet is connected and a role is selected.
  • The role persists correctly across different sections of the app.
  • No UI/UX inconsistencies arise from this change.

Commit changes:

git commit -m "Feature: Implement dynamic role-based dashboard and wallet connection"
@gchyuli gchyuli added ODBuild Further information is requested External contributors Manteiner - Yuli labels Feb 24, 2025
@gchyuli gchyuli changed the title Dynamic Role Dashboard Dynamic Role-Based Dashboard and Wallet Connection Feb 24, 2025
@kcmikee
Copy link

kcmikee commented Feb 24, 2025

Hi Team,

I’m Mike, a Diamond-tier contributor with extensive experience in frontend development and state management, particularly in building dynamic, role-based dashboards for decentralized applications. I’ve worked on similar features where user roles dictate UI updates, ensuring seamless transitions and persistent state management.

I’d like to take on the task of removing the "Clear Role" button and implementing a dynamic dashboard that updates based on the user’s selected role during wallet connection.

Looking forward to contributing

@OgbuGideon
Copy link

Hi, my name is Gideon and i am a front-end developer with experience solving problems using front-end technologies such as typescript, javascript and react. This is my first time contributing on this platform. I have gone through the projects and i am particularly interested in contributing to this. I am very confident that i can deliver this within the specified time. ETA <=24hrs

@gchyuli gchyuli assigned gchyuli and kcmikee and unassigned gchyuli Feb 24, 2025
@gchyuli
Copy link
Collaborator Author

gchyuli commented Feb 24, 2025

Hi @kcmikee if you need help with some aspect, can tell us!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants