refactors answers codes to parse user data from jwt token. Moves pars…

[qckpckt]

…eToken to seperate file to be imported to avoid duplication

Motivation

Relating to this trello board task, and this issue, and maybe this issue too?

Implementation

• Moved parsetoken (renamed to camel case) to separate file (common.js) to be imported by both userList.js and questionList.js
• Updated parseAnswer logic to read user data from jwt token
• Updated addAnswer and editAnswer to use the new user data fields generated by parseAnswer

To do

• ensure that the client methods that call the add/edit answer can provide the jwt token in the request body? (not sure if this is in scope for this ticket)
• test that it actually works

Unknowns

• the github issue called for location. I can see country in the user object -- hopefully that's enough?

[aviskarkc10]

better to use camelCase variable naming. Will make our code consistent

[sethuraj]

Hi @aviskarkc10 The class variables for the class user is matched with how the fields in the NoSQL container. CosmosDB is case sensitive. In C# we can map the class variable to database field , not sure how it is in node.js, so kept exactly the same. That is my code. We can discuss more in slack. Thanks

[aviskarkc10]

shouldn't name be null when anonymous is true? I am thinking this should be reversed?

[sethuraj]

Hi @aviskarkc10 If anonymous, we should call it "Anonymous". I am going to merge this code from Alex to test and test. Thanks Jay

[sethuraj]

This will be reversed. I will make this change.
const userDetails = {
id: userData.id,
name: userData.anonymous ? "Dr. Anonymous" : userData.fullname
}

[qckpckt]

Yes this should be reversed. Sorry!