Add reporting if resource is outdated, broken, duplicate ⛔️

colorstackorg / oyster

Monorepo that houses ColorStack's core product software.

MIT License

283 stars 140 forks source link

Add reporting if resource is outdated, broken, duplicate ⛔️ #270

Open ramiAbdou opened 5 months ago

ramiAbdou commented 5 months ago

Description

This feature will add reporting to the Resource Database so that the database can be moderated by the community.

Acceptance Criteria

Here is how this flow should work:

User clicks on the "More Options" but, which should replace the "Copy Resource Link" button that currently exists.
A dropdown should open with the following options:
- "Copy Resource Link"
- "Report Issue"
When clicking "Report Issue", it should navigate the URL to /resources/:id/report, which opens up a modal. That modal should show a form with the following field:
- Reason: Should be one of:
- "Resource is outdated."
- "Link is broken."
- "This is a duplicate."

Upon submitting the form, the poster of the resource should get a Slack notification about it saying something like:

A resource you posted was reported as [outdated/broken/a duplicate]. Please review and delete the resource if this report is accurate.

Note, we should save the report in the database as well.

DiegoLopezInc commented 5 months ago

I am interested in working on this!

ramiAbdou commented 5 months ago

It's yours @PineappleFarms! Check back EOD tomorrow for some more context on this issue!

DiegoLopezInc commented 5 months ago

Looking forward to it! I'll set my self up by following the contribution guide in the meantime.

ramiAbdou commented 5 months ago

Hey @PineappleFarms, sorry for the delay but I added some additional notes in the issue! Let me know if you have solid direction to get started!

tomas-salgado commented 5 months ago

Hey @PineappleFarms, are you still working on this issue? No worries if not, just let me know so we can open it up for someone else!

DiegoLopezInc commented 5 months ago

Hey @tomas-salgado I'd like to take a crack at this, let me make some progress tomorrow morning. If I get stuck I'll pass it on!

tomas-salgado commented 5 months ago

Sounds good! Feel free to reach out if you have any questions

tomas-salgado commented 3 months ago

Going to open up this issue!

melyssa5 commented 3 months ago

Hi, can I claim this issue?

tomas-salgado commented 3 months ago

@melyssa5 you've got it!

tomas-salgado commented 2 months ago

@melyssa5 are you still working on this? No worries if not, I'll open the issue soon

melyssa5 commented 2 months ago

@tomas-salgado Hi, sorry for the lack of update. Yes, I slowed down this week due to my internship wrapping up, but I'm continuing tomorrow.

DavidUmanzor commented 1 month ago

Hello, is this open to being claimed? Just finished setting up my local environment so I'll start looking into it while waiting.

tomas-salgado commented 1 month ago

@DavidUmanzor you've got it!

DavidUmanzor commented 1 month ago

Quick Update, this is the current look for the button now, I need to hook up the report button, but this is just the front-end work done.

Any tracking can be done on my branch at https://github.com/DavidUmanzor/oyster/tree/add-resource-reporting

tomas-salgado commented 1 week ago

Hey @DavidUmanzor! Do you almost have a PR up for this?

DavidUmanzor commented 1 week ago

Hey @tomas-salgado not yet, I hope to have something for you soon.