Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Could it be better if Profile contains a User? So that everything will be in Profile directly or indirectly. Or maybe the other way, a User containing a Profile.
-
b2plane63801y@cafecortado right now i have modeled the Profile by adding the missing fields plus a 1-to-1 relationship with User model. That way I'll be able to use joins to fetch data from user and additional data for profile. Does that make sense or is it a sloppy database modeling design?
-
b2plane63801y@Lensflare what do you mean?
Please correct me if i have the wrong way of thinking. Maybe im right but at as complexity increases i keep having second doubts. I just need to discuss about it with another dev but i have no partner right now. So discussing here helps -
@b2plane I was referring to your last comment where you implied that your models are aware of your DB design because you mentioned 1-to-1 and joins.
I have a question about modeling a UI to code
Lets say you have a UI finished
Now you need to model it to code
For simplicity ignore functionality just focus on designing the model classes
For further simplicity Imagine that the UI is grouped into material cards.
Lets say the UI of the User Profile Page looks like this:
1) HEADER
- user profile banner
- user profile image
- username
- first and last name
- total posts
- total likes
- button to add to favorites
- dropdown to report user
- button to share profile
2) BIO
- short description
- user birthday
- location
3) ANNOYNCEMENTS
- "X% off on Y"
- "going live at X:YZ"
- etc
4) GALLERY
- group of images posted on profile timeline
5) TIMELINE
- text/video/audio
- number of likes on post
- user profile image
- username
- user first and last name
- post date
- etc
---
Now im having a mixed feeling what is right thing to do. In my User model i have a date of birth field among other fields as well as profile image url to s3 bucket. This means that i already have half the information for HEADER card from User model, but now i would need to create a Profile model to fill in the remaining fields.
Especially for BIO card:
- short description (Profile model)
- user birthday (User model)
- location (Profile model)
Is this weird? Mixing data with 2 models on 1 page on 1 or multiple card sections?
This feels messy to me and as if im gonna hit a wall if i continue long enough like this. A better solution to me is to have a Profile model handle everything on the Profile page and be able to cover all cards and fields on each card. But this doesnt seem like a realistic or possible way to do it since specific fields are required for User model.
Am i overcomplicating and overthinking this shit?
Tell me is it normal to mix 2 or more different models to show data in 1 card on 1 page or how would you suggest doing it better?
rant