FEATURE REQUEST: Connect Frontend With Backend User System

[PinJinx]

Is your feature request related to a problem?

• Yes, it is related to a problem

Describe the feature you'd like

🌟 Feature Description

Our backend now includes a complete users table and several related entities, but the frontend still relies on mock user data. As a result, the Profile page does not display actual authenticated user information, and backend-linked records are reflected in the UI.

🔍 Problem Statement

The Profile page still uses mock data and does not display real user information. Additionally, both the frontend and backend independently connect to Supabase, causing duplication and inconsistent data handling. The frontend needs to stop using mock data and rely solely on backend-managed user data.

🎯 Expected Outcome

• Replace all mock data on the Profile page with real user data coming from backend API endpoints.
• Ensure proper linkage between the authenticated user and their backend-stored profile record.
• Implement clear loading, error, and empty UI states.
• Maintain full type safety through TypeScript interfaces consistent with the backend schema.

📷 Screenshots and Design Ideas

📋 Additional Context

I hoped to create endpoints in the backend and manage the supase stuff in the backend itself currently both front end and back end connects to supa base for fetching data and retrieving things. This is unnecessary and wasting resources.I thought we could migrate everything to the back end.

Record

• I agree to follow this project's Code of Conduct
• I want to work on implementing this feature

[smokeyScraper]

Seems reasonable. This indeed is static and needed a revamp. Thanks a lot!

[smokeyScraper]

Hey @PinJinx. Are you still working on this?

[smokeyScraper]

There's a problem that you might face over this is that all the data of the users of the bot, as well as the ones who are maintainers of Orgs and instantiate the bot, is stored in the same table. Therefore, a user can have two tuples for themselves (only the owner), which I think can be segregated by the Email identifier, as Discord data doesn't store it.
Discuss your plan for implementing this, and let's connect if there are any issues that may arise.

[PinJinx]

Hey @smokeyScraper, sorry for the delay and thanks for your patience. I’ve been out of station for the past few days.
I’ll get back to you on this as soon as I’m back at college (in about 2–3 days) and have proper access to everything. I do have a plan in mind, and I’ll send you the full details as soon as possible so we can discuss any changes before I begin working on it.
Thanks again for your patience!