📙 Notes for extending Parse.User

Link to section:
Parse.Object

What is the issue?
When extending Parse.User it is not very obvious, that the registerSubclass call does not follow the normal convention of passing the name of the subclass as a string followed by the subclass itself. Instead, the name of the class being extended "_User" is supplied. This is easy to overlook and also, there is no explanation of why it should be done differently here. In fact, this nearly lead me into creating an issue for the JS SDK after several hours of debugging and trying around...

Can you propose a solution?
Adding a paragraph (beginning with "⚠️") that points this out and maybe also explains the background why this is required.

Additional comments
Do I understand correctly, that the registerSubclass call is NOT used to add another JS type to be used for instantiating a Parse class but instead to overwrite which JS type is used for instantiating the Parse class "_User"?
The existence and use case for Parse.User.allowCustomUserClass should probably be explained here also.

Start at the linked Parse.Object section in the documentation and review the guidance for extending Parse.User, including registerSubclass and Parse.User.allowCustomUserClass. Add a warning paragraph explaining how this call differs from the usual subclass registration convention and clarify its purpose.