deepbig / 42matcha Goto Github PK

After click the Tag Tab.

• TypeError: Cannot read property 'length' of undefined
  src/components/unit/profile/myself/index.jsx:105

After type some words in tag field.

• Unhandled Rejection (TypeError): Cannot read property 'map' of undefined
  src/components/unit/profile/myself/index.jsx:114

After click Add button.

• TypeError: user.tag1 is not iterable
  _handleCheckDuplicate
  src/components/unit/profile/myself/index.jsx:66

Provide search option based on the user's prefer tags.

• Delete after update.

• Delete after click delete button.

• Should NOT delete default.png.

• Google OAuth

• Using Its image

test with these:

• Login with Fake account

• Login in with registered account

• Login in with un-verified account

My guessing is the error generated in pull/user.

Here is the log:

GET /api/tags?type=preference 304 137.446 ms - -
GET /api/tags?type=myself 304 140.900 ms - -
GET /api/blocks 304 138.228 ms - -
GET /api/notifications 304 137.980 ms - -
GET /api/users?userId=-1 304 138.724 ms - -
GET /api/likes?type=chat 304 288.157 ms - `-`
GET /api/overviews 304 290.077 ms - -
GET /api/likes?type=follow 304 422.576 ms - -

• Not able to edit.

• API code does not work.

Each user must have a popularity score. Ask the student to explain his strategy to calculate this score, it must be consistent and a minimum relevant.

Popularity score = like - dislike

Options:

• Add popularity column in the user's table, and update when a user clicks like or dislike.
    Pros:
      - don't need to make multiple connections when a user searches.
    Cons:
      - Heavy work on like and dislike (user can click like and dislike multiple times and     it will affect user tables and I don't know how effectively change both tables.

• calculate when it needed (when a user clicks profile or searches match).
    Pros:
      - minimize process to update.
    Cons:
      - Difficult to make calculation. (1. join tables, and count numbers of likes and dislikes per user and calculate all user's popularity, and apply them to search results.)

The decision I made:

• Add popularity column in the user's table, and update when a user clicks like or dislike.

• Update User table with popularity column.

• Update user's likes and dislikes action (apply to the affected user's data)

• Apply the information in the user's profile.

• 304 error test after all basic info update

• Does all page load properly?

• Does email work properly?

• Does Socket works properly?

• Does Report function works properly?

• Does OAuth works properly?

• Does CSS works properly?

Potential part of error:

1. Frontend - component - template - core
2. backend - app.js - io connection part

• Does not generate Alert

• Does not generate Alert After sent email (Only Console says signup success)

• Failed email sent

• Backend does not response.

• Not matching password does not generate correct error.

• Email verification does not work properly. (fix the link)
  *** Verifies id is created during Auth sign up. also, being used in Verifies and Mail.