-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
Replacement/just removal and deprecation of getDiscriminatedName
#1245
Comments
getDiscriminatedName
Regarding this, as the user no longer has a discriminator it could be made where getUserName provides you with the @ userName and getGlobalName gets there display Name. getDiscriminatedName should be marked as @deprecated but no removed until bots migrate too |
There are still regular users with discriminators |
Majority have migrated but I said keep it |
You should not deprecate something which should be used imo |
but it will be removed in the future. |
@TheKodeToad if you wish you can have a look at the pr i made a while back and see if you have any suggestions for amendment. |
Well, the PR's merge will need to be delayed. |
why. you need make users aware. |
What feature are you proposing?
getDiscriminatedName
is no longer desirable as users who've migrated to the new username system will have no discriminator (represented as 0). I personally don't think changing the behaviour of the method is a good idea as the name implies that it will have a discriminator!The method could have a replacement which drops #0... however at some point both
getDiscriminatedName
and this method will become uselessDo you have any additional material for your feature proposal?
No response
The text was updated successfully, but these errors were encountered: