if the person is the caller, they may want to know what position in the table they'll be, but right now it shows the person as the #9, even if they were the 100. To solve this will require to change how the call for mongo works, and maybe refactoring all calls to also improve speed and reduce db calls.
if the person is the caller, they may want to know what position in the table they'll be, but right now it shows the person as the #9, even if they were the 100. To solve this will require to change how the call for mongo works, and maybe refactoring all calls to also improve speed and reduce db calls.