New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(UserPremiumType): add NitroBasic
#616
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Is this actually right? Isn't this completely breaking? |
This is supposed to be right, Nitro Basic was officially announced and is being rolled out since today. Discord is using |
I think I interpreted 0 as no Nitro rather than unused, I guess... |
Now, if you don't have Nitro, the user object will return the |
It wouldn't really make sense, discord/discord-api-docs#5568 is probably the way it is being done |
I bought the new nitro to check and, yep, comes in as 3 afaik it was 0 with no nitro being set to -1 or the field being made nullable but that caused too many issues because it was (obviously) a breaking change. As of the rollout this week, it's 3. No nitro is still 0. |
I bought Nitro Basic and now I can confirm that it is 3. I will change it and sorry for the confusion. |
Please describe the changes this PR makes and why it should be merged:
If applicable, please reference Discord API Docs PRs or commits that influenced this PR: