Added suggestAvailableUsername helper function (src/user/profile.js ; src/topics/create.js ; public/src/client/register.js): Suggest a unique username

[Dcano-png]

Recitation 3: Software Archaeology

1. Issue

Full path to the refactored file:
src/user/profile.js
src/topics/create.js
public/src/client/register.js

What do you think this file does?
src/user/profile.js : I believe handles the back end of what the user decides to change/interact with their account/profile.
src/topics/create.js: I believe it handles with the back end of topics.
public/src/client/register.js: I believe handles the front end of when a client registers/creates a new account.

What is the scope of your refactoring within that file(s)?
I added the helper function suggestAvailableUsername so that when the taken username error pops up, there is a suggested username generated.

2. Refactoring

How did the specific issue you chose impact the codebase’s adaptability?
Having suggested available usernames ensures that all usernames are unique and helps the user experience when registering.

What changes did you make to resolve the issue?
The added helper function does not trigger, which can be a calling issue, making the change not reflected in the push. Also, an issue of changing multiple files rather than just one.

How do your changes improve adaptability? Did you consider alternatives?
The change is not in use, making it hurt the code's adaptability. Potential alternatives is to revert the code and solely change the public/src/client/register.js file.

3. Validation

How did you trigger the refactored code path from the UI?
I have yet to see the refactored code be triggered and shown in the UI.