[Profile Showcase Popup backend]: Backend needed for delegates

[alexandraB99]

Description

• Social links model with at least url and domain
• FIGMA permissionsModel and allTokenRequirementsMet in Communities Model
• userHas (this shows if the user has >1 of a given collectible, some variants showing what we do as that number increases is shown here: FIGMA
• ManageCollectiblesModel: we need to know if the collectible belongs to a community and the community id, and/or the url and domain FIGMA
• Assets will need an address to view on GoinGekko (figma) as well as communityName and communityId

[MishkaRogachev]

My vision of what the backend should provide:

• Communities:
  • base communities model (same model as for preferences aka main communities model)
  • profile communities model (showcaseKey/communityId), position from natural list order
• Accounts
  • profile accounts model (address, name, colorId, emoji), position from natural list order
• Collectibles
  • base collectibles model, a dedicated model in profile/contacts section configured with visible contact's wallet addresses
  • profile collectibles model (showcaseKey/chainID+contractAddress+TokenID), position from natural list order
  • Verified Tokens:
  • base tokens model, a dedicated model in profile/contacts section configured with visible contact's wallet addresses to get valid balances:
  • profile tokens model (showcaseKey/symbol), position from natural list order.
  • Unverified Tokens:
  • base tokens model, a dedicated model in profile/contacts section configured with visible contact's wallet addresses to get valid balances:
  • profile tokens model (showcaseKey/chainID+contractAddress), position from natural list order.
• Social Links
  • profile social links model (url, name), position from natural list order

[alexjba]

@alexandraB99 The new backend will use a different models structure and most of the data required for the new delegates should be there once the profile showcase is integrated.

Social links model with at least url and domain

The domain could be fetched in the UI. We'll probably need a helper function for this.

FIGMA permissionsModel and allTokenRequirementsMet in Communities Model

We need to check if the main communities model contains the permissionsModel as well. We will use this model in the showcase. Otherwise we need another approach. (probably another task to tackle this) @alexandraB99 who do we need allTokenRequirementsMet? I see in the designs the lock indicator when a community has permissions, but I can't spot the case where we need to check if the allTokenRequirementsMet.

userHas (this shows if the user has >1 of a given collectible, some variants showing what we do as that number increases is shown here:

Check balance property in the main collectibles model. If the main wallet model supports this, we should have it in the showcase models as well.

ManageCollectiblesModel: we need to know if the collectible belongs to a community and the community id, and/or the url and domain FIGMA

Already supported in the main wallet model. We'll use the same model for profile showcase.

Assets will need an address to view on GoinGekko (figma) as well as communityName and communityId

We'll probably use the same approach as for the collectibles. If we have this in the main wallet model it's fine. Otherwise we'll probably need to add it there. TBD

[jrainville]

Moving Profile showcase issues to 2.30 for now as it's no longer priority