This repository was archived by the owner on Nov 20, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
This repository was archived by the owner on Nov 20, 2025. It is now read-only.
Challenges - todo #63
Copy link
Copy link
Open
Description
- write general tests for ideas and challenges
- write a general model for ideas and challenges
- generalize validation or not
- generalize controllers or not
- generalize serializers or not
- goto for challenges
THE SAME AS IN IDEAS:
- create a challenge
- read challenge by id
- update challenge
- challenge tags
- add
- read
- remove
- list challenges
- with tags
- created by somebody
- commented by somebody
- with my tags
- new
- random
- highly rated
- trending
related to other challenges by tags(do later)
- search challenges by title (only if feasible)
- owner (creator) can edit a challenge
delete(needs more thinking)- vote
- comments and reactions to comments
- create comment
- read comments of the challenge
- update comment
- delete comment
- vote comment
- CRUD reaction
vote reactions(someday, maybe)
- watch challenge
- watch, unwatch
- count watches
- see users who watch
- see what ideas a set of users watch
- notify users who watch.
- What is the difference between watching, subscribing (wanting to be notified), and expressing interest in the challenge (as in "I care about this")? Is it the same?
- make challenges (in limited form) visible to non-logged users.
It is so far the common 'figure out' with #43
- Probably needs a separate issue?
Figure out:
- how to collaboratively work on challenges
- how to group similar or duplicate challenges
- how to reference challenges between each other
- what about tag popularity etc.
- challenge creator: reference or edge?
Metadata
Metadata
Assignees
Labels
No labels