Split Discord Module #238
Replies: 2 comments 6 replies
-
The interface SocialItem should have a type for icon determination: export type supportedSocials = 'discord' | 'twitter' | 'github' | 'other'
export interface SocialItem {
name: string;
url: string;
type: supportedSocials;
} The export interface Milestone {
title: string;
date: Date;
icon: string;
color: string;
description: string;
url?: string;
} Also, profiles, we need the avatar key if we use Discord ids and not github ones export interface Profiles {
_id: string; //userid from Discord in case Discord is the single-source of truth for this, when using the discord-id we may populate this even with the stats from the discord module
bio: string;
profiles: {
twitter: SocialItem;
github: SocialItem; // the ones added here need to be discussed, but imo definitely not generic
};
milestones: Milestone[]
} I think there is lot more than just DiscordStats for DiscordEvents 🤔 There was a recent discussion on making Katra signups work with our events on Discord |
Beta Was this translation helpful? Give feedback.
-
When creating the module, would you split Socials and Milestones to seperate Entities, or would you just put them as properties from the socials-entity @eddiejaoude ? I'm still not quite sure if its the best to transfer them as |
Beta Was this translation helpful? Give feedback.
-
See the discussion here. We may want to split the current
Discord
toProfiles
andDiscordEvents
The
Profile
one could have the following DTO:The
DiscordEvents
the following:when using the same ID, populating each other shouldn't be hard so we can even get the Data from both objects.
Especially for
Profile
we definitely need to think of a solution for creating or deleting a milestone then, if its stored in an array. Maybe this needs to be extracted to a collection as well 🤔Let me know what you think and if its worth to create a bit more in-detail concepts for this
Beta Was this translation helpful? Give feedback.
All reactions