You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to make fewer endpoint requests, I believe it is imperative to have to more properties within each profile object:
matches: [ profile_id, profile_id, profile_id ], ** and array of profile_ids of matches... not full objects
role: "mentee" || "mentor"
Reason for Matches Array
Without these properties stored within the Profile Object, I will then have to take the profile_id and request from matches/all/obj and then find the profile_id that matches... but even then there are some issues.
Reason for Role:
This makes sorting data immediately easier rather than searching a separate endpoint for the role name. For Example: when we use get all to occupy User Management page, there is a column filtering roles.
From here we can grab other information using other endpoints if the user chooses to progress...
The text was updated successfully, but these errors were encountered:
In order to make fewer endpoint requests, I believe it is imperative to have to more properties within each profile object:
matches: [ profile_id, profile_id, profile_id ], ** and array of profile_ids of matches... not full objects
role: "mentee" || "mentor"
Reason for Matches Array
Without these properties stored within the Profile Object, I will then have to take the profile_id and request from matches/all/obj and then find the profile_id that matches... but even then there are some issues.
Reason for Role:
This makes sorting data immediately easier rather than searching a separate endpoint for the role name. For Example: when we use get all to occupy User Management page, there is a column filtering roles.
From here we can grab other information using other endpoints if the user chooses to progress...
The text was updated successfully, but these errors were encountered: