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.

Sign up for GitHub

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

Jump to bottom

Give users the ability to "close" entries (see: 'active': boolean) #30

Open
lpatmo opened this issue Mar 2, 2019 · 3 comments
Open

Give users the ability to "close" entries (see: 'active': boolean) #30

lpatmo opened this issue Mar 2, 2019 · 3 comments
Labels
[priority] high High-priority issues [state] backlog The issue has been raised but hasn't yet been looked at, we'll get to it [tech] javascript Resolution is likely to involve JavaScript [tech] meteorjs Resolution is likely to require basic understanding of MeteorJS [tech] react Resolution is likely to involve ReactJS
Milestone
MVP v1.0.1

Comments

@lpatmo
Copy link
Member

lpatmo commented Mar 2, 2019 •
edited
Loading

  • A user should be able to click to "expire" an entry by editing their unmatched entries from the dashboard
  • A moderator should be able to click to "expire" an entry if they see that it is spam, etc.
@lpatmo lpatmo added [tech] javascript Resolution is likely to involve JavaScript [tech] meteorjs Resolution is likely to require basic understanding of MeteorJS [tech] react Resolution is likely to involve ReactJS labels Apr 2, 2019
@distalx
Copy link
Member

distalx commented Apr 4, 2019

some thoughts.

What if user can active/inactive their entries instead of 'expire'. Just to keep it consistent. And We do have active flag for this reason.

And if an entry is a spam, moderator should mark that entry as a 'spam' and not as 'expire' or 'inactive'. Because if we use the same flag/field for moderator & users then user can simply override flag.

@lpatmo
Copy link
Member Author

lpatmo commented Apr 4, 2019

Ah, that makes sense! Thanks for the thought.

So, active -> true or false.
spam -> true or false.

@lpatmo lpatmo changed the title Entry expiration Give users the ability to "close" entries (see: 'active': boolean) Apr 6, 2019
@angelocordon angelocordon added this to the MVP v1.0.1 milestone Apr 6, 2019
@angelocordon angelocordon added the [state] backlog The issue has been raised but hasn't yet been looked at, we'll get to it label Apr 6, 2019
@angelocordon
Copy link
Contributor

Ok to set with [state] backlog for now? I think it might be safe to move to the next phase; perhaps in the meantime, we can expire entries manually in the console.

@lpatmo lpatmo mentioned this issue Apr 7, 2019
Open
@lpatmo lpatmo added the [priority] high High-priority issues label Apr 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[priority] high High-priority issues [state] backlog The issue has been raised but hasn't yet been looked at, we'll get to it [tech] javascript Resolution is likely to involve JavaScript [tech] meteorjs Resolution is likely to require basic understanding of MeteorJS [tech] react Resolution is likely to involve ReactJS
Projects
None yet
Milestone
MVP v1.0.1
Development

No branches or pull requests
3 participants
@angelocordon @lpatmo @distalx