Description:

The registration subpage. Post data to backend not implemented yet. The user data can check on the console.

This page can be checked via /signup.

All user data are required. Otherwise, it will hint the user to type their data.

The password should be more than five characters.

After user type their data correctly, it will hint "Account Created!", Click the "Close" button the page will navigate to the landing page.

All Submissions:

• [x] Have you followed the guidelines in our Contributing document?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [x] My code follows the code style of this project
• [ ] My code has been commented
• [ ] My change requires a change to the documentation
• [ ] I have updated the documentation accordingly
• [ ] I have added tests to cover my changes
• [ ] All new and existing tests passed

Description:

Fixes #161 . Changed the post card to match the design of the one on Figma

Also added activity statuses for posts on the user profile.

All Submissions:

• [x] Have you followed the guidelines in our Contributing document?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [x] My code follows the code style of this project
• [ ] My code has been commented
• [ ] My change requires a change to the documentation
• [ ] I have updated the documentation accordingly
• [ ] I have added tests to cover my changes
• [ ] All new and existing tests passed

Description:

Fixes #162

• Implemented a comment component that pops up when a user clicks the comment button on a post
• Shows tags and handles properly using PR #189
• Uses post input and multiple other components in the modal
• submitForm() function in CommentController still needs to be implemented (waiting on backend) for posting the comment to API

All Submissions:

• [x] Have you followed the guidelines in our Contributing document?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [x] My code follows the code style of this project
• [x] My code has been commented
• [ ] My change requires a change to the documentation
• [ ] I have updated the documentation accordingly
• [ ] I have added tests to cover my changes
• [x] All new and existing tests passed

Is your feature request related to a problem? Please describe. The endpoint for activities doesn't support activity text describing the action the user took on the post

Describe the solution you'd like Include activity text as part of the payload when retrieving data from the activity endpoint

Describe alternatives you've considered

Additional context

Is your feature request related to a problem? Please describe. The search bar is currently not implemented on the frontend. The search feature will allow users to search for posts, topics and users.

Describe the solution you'd like The solution will implement a search bar which will find matches based on a search request for specific posts, topics, users, etc. The results will be displayed in a list view for the user. The design should follow the Figma mock-ups.

The user can search in three categories: Top, Latest and People.

• Top will show the best match search results.
• Latest will show the most recent search results.
• People will show any users who match the search.

This search feature will not implement a drop down of recommended search finds, it will only output the final search results.

Describe alternatives you've considered n/a

Additional context This issue was discussed, approved and allocated at the front-end team meeting on 24/03/22.

Is your feature request related to a problem? Please describe. The users wants to change customize the banner.

Describe the solution you'd like Use a MUI dialog to produce a pop up and grid for positioning things.

Describe alternatives you've considered N/A

Additional context N/A

Is your feature request related to a problem? Please describe. I want to be able to group posts based on a certain tag, or search based on the concept of tags

Describe the solution you'd like A new model will be created for the database and backend to allow for the concept of tags

TAG (PK) TAG_ID: INTEGER TAG_NAME: STRING

POST_TAG (PK) ID: INTEGER (FK) TAG_ID: INTEGER (FK) POST_ID: INTEGER Constraint: Unique(TAG_ID, POST_ID)

Describe alternatives you've considered Could just perform manual searches on all posts text to find the tag we are interested in (very inefficient)

The model could be changed slightly, but this simple method results in more rows but is easy for querying easily

Additional context Add any other context or screenshots about the feature request here.

Description:

Adds an apostrophe in the correct spot on the landing page.

Also applies latest ESLint formatting to LandingView.jsx

Closes #133

All Submissions:

• [x] Have you followed the guidelines in our Contributing document?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [x] My code follows the code style of this project
• [ ] My code has been commented
• [ ] My change requires a change to the documentation
• [ ] I have updated the documentation accordingly
• [ ] I have added tests to cover my changes
• [ ] All new and existing tests passed

Is your feature request related to a problem? Please describe. Currently we do not have endpoints for liking or unliking posts

Describe the solution you'd like

• Implement two endpoints: POST /posts/:id/like for liking a post (does not require a body) and DELETE /posts/:id/like for unliking a post. Those endpoints should automatically add/remove entries from the liked-posts table

Add tests for the two endpoints

Describe the bug Backend getActivity does not support the COMMENT type. It considers all comments to be just the post the user creates.

To Reproduce Steps to reproduce the behavior:

1. try to get activity for a comment
2. display comment as a post instead of a comment

Expected behavior Comments should display as COMMENT type activity instead of POST type activity

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.

Is your feature request related to a problem? Please describe. Documentation in the wiki relating to the redesign of the UI as done by Team 1.

Describe the solution you'd like A wiki page documenting the changes between V1 and V2.

Describe alternatives you've considered

Additional context

Description:

Please provide a summary of changes made and the relevant issue that has been worked on. Also list any major changes made to project structure/dependencies if applicable

Closes #136

All Submissions:

• [x] Have you followed the guidelines in our Contributing document?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [x] My code follows the code style of this project
• [ ] My code has been commented
• [ ] My change requires a change to the documentation
• [ ] I have updated the documentation accordingly
• [ ] I have added tests to cover my changes
• [x] All new and existing tests passed

NOTE: I have no posts in my database, they would nominally show below the new post button

Is your feature request related to a problem? Please describe. I am not able to delete any of my posts

Describe the solution you'd like There should be a button on my posts where I can delete them, and I shouldn't be able to delete other users' posts.

Describe alternatives you've considered N/A

Additional context N/A

Is your feature request related to a problem? Please describe. I want to be able to share videos and images with my posts

Describe the solution you'd like

• Add a button to attach a file when making a new post
• Display attachments on posts

Describe alternatives you've considered N/A

Additional context N/A

Is your feature request related to a problem? Please describe. Currently, Updog is designed exclusively with mobile devices in mind. When using Updog with a desktop aspect ratio, the UI is unattractive and difficult to use.

Describe the solution you'd like The dashboard should be checked to see how it responds and looks at a desktop aspect ratio. If not satisfactory, the page should have a desktop version designed for it. Each page that requires a substantial redesign may be broken out into a sub-issue.

Design from Figma by A2

Describe alternatives you've considered N/A

Additional context N/A

Is your feature request related to a problem? Please describe. Currently, when deleting a user or a post, all the the tables in the database such as likedPost and sharedPost will still reference the ids of the non-existent user or post. We want those tuples that reference non-existent users and posts to be deleted. Furthermore, for post we need to get rid of attachments with the deleted post's id, and for users will need to delete follows that link to deleted accounts.

Describe the solution you'd like When deleting a user or post, all the tuples that reference that user or post must also be deleted.