Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments layout functions #34

Merged
merged 9 commits into from
Dec 3, 2022
Merged

Comments layout functions #34

merged 9 commits into from
Dec 3, 2022

Conversation

Ofarouq310
Copy link
Collaborator

Summary of branch implementations:

- Upon the user click on the (Comments) button on the homepage layout:

  • When the user clicks on the "Comment" button, the data is recorded in the [Involvement API] and the screen is updated.
  • When the popup loads, the webapp retrieves data from the [Involvement API] to show the item comments.
  • The total number of existing comments is displayed in the comments section.

  • Reorganize project files and folders.

Please, refer to task details, if needed:
#11, #8, #5.

Copy link
Collaborator

@BryteLitty BryteLitty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Ofarouq310,

Great job so far!
Your milestone is complete! There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
CongratulationsGraduationGIF

Highlights

  • No linter errors ✔️
  • Descriptive commit message ✔️
  • Milestone works as expected ✔️
  • Correct gitflow use ✔️

###Required Changes
N/A

Optional Changes

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you take them into account as they can make your code better.

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants