Unfuck DiscordLink and Invitation API
Closed this issue · 2 comments
rconjoe commented
They both work fine but they overlap and the process should be setup so that the queries for provana user data made by the bot after link can follow the same pattern regardless of user type.
Creators
1. Invitation entry is created at alphacode creation
2. DiscordLink entry is created during registration (inv association)
Supporters
1. 'discord' field is populated with link code at registration
2. DiscordLink entry created when code is fed to bot
rconjoe commented
The simplest way to do this would be to hack in DiscordLink association inside of Invitation association. This violates every single design principle in the API except shortest route to goal. HOWEVER...it's an auxilary feature being replaced in the frontend's 1.0. So if there is a place to chill out, it's here.