yeppog / allez Goto Github PK

Ensure during the registration process the usernames are unique. This is to make profile search easier

user api docs need to reflect new methods and schemas

As per title

Create the CommentComponent.

Refer to the schema:

export interface Comment {
  comments: Comment[];
  body: string;
  edited: boolean;
  username: string;
  avatarPath: string;
  createdAt: Date;
}

The component should take in the above props, and map it into a format similar to the post component. Refer to the illustration:

The reply button should open an input field for the user to reply to the comment.
The like button should not do anything for now.

Afterwards, update PostPageComponent to take in the new mapping for comments.

Need to add the following to the API:

• Delete existing avatar from server to free up space when replacing avatar
• Updating of other user details

Should remove unnecessary files from the server when they are no longer in use.

? - Keep an array of pointers to the old profile pictures to access them??

Currently the only places that have proper user flows are in LoginComponent and RegisterComponent.

Error handling and passing error messages are required for the following components:

• LoginComponent

• Handle account not activated error

• RegisterComponent

• Handle existing username and email error

• ProfileEditComponent

• Handle validity of form (must not be empty)

As per title. Ensure that it fetches chronologically

As per title. Low data fetch users from database query based on matching characters.

The create post workflow should have the following items:

• Add media button (accesses the phone file system => upload file button essentially)
• Camera button (launches the device camera, desktop accesses the webcam (should be of similar functionality))
• Post body
• Tags

Refer to swagger API for the neccesary request body parameters.

Expose the updated values to update state immediately.

Warning: Cannot update during an existing state transition (such as within `render`). Render methods should be a pure function of props and state.
    at LoginComponent (http://localhost:3000/static/js/main.chunk.js:1295:64)
    at Route (http://localhost:3000/static/js/vendors~main.chunk.js:236276:29)
    at Switch (http://localhost:3000/static/js/vendors~main.chunk.js:236478:29)
    at div
    at ThemeProvider (http://localhost:3000/static/js/vendors~main.chunk.js:185082:24)
    at App (http://localhost:3000/main.011ecfa4ce5efa712c51.hot-update.js:66:84)
    at Router (http://localhost:3000/static/js/vendors~main.chunk.js:235911:30)
    at BrowserRouter (http://localhost:3000/static/js/vendors~main.chunk.js:235531:35)
    at Provider (http://localhost:3000/static/js/vendors~main.chunk.js:232880:20)

Probably something to do with the redirects.

• Make a better ProtectedRoute Component
• Implement prop passing through Protected Route

Increase code coverage. Also exclude files that cannot be tested

As per title. Create the schema and allow for addition, deletion and editing of routes.

Should have the following parameters:

• created at
• name
• gym
• grade
• color
• mediaPath
• posts (object reference)