Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
c3a8497 to
8bdf435
Compare
alannnc
reviewed
Sep 18, 2022
apps/web/components/ui/UsernameAvailability/PremiumTextfield.tsx
Outdated
Show resolved
Hide resolved
…k' into add-premium-text-field-input-back
emrysal
reviewed
Sep 19, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Loom
Important
In current flow, if a username is already premium it is assumed that
So, short usernames that are in our seed are considered Premium and they don't require payment to change to a new premium username. This is the reason @alannnc that for pro username it wasn't considering it as an upgrade when you try to choose a premium username.
This was done because I analyzed some of the metadata that we have in DB and found out that some of the premium usernames don't have user.metadata.isPremium set to true. It might be due to the reason that user.metadata.isPremium logic might have been added later on
Follow up