* Pluck over map
* Explain why map makes sense there
* Refactor reactions controller a bit and iterate only once
* Use group by instead of N counting queries
* More positive
* Simplify BufferedArticlesController
* Less queries for MailchimpBot
* Use Rails instead of SQL
* Build comment_ids only when needed
* remove border from ad and fix cut-off
* improving ellipsis for tags
* improving ellipsis for tags
* fixing underline between each tag on hover
* user avatars alignment in left sidebar
* test commit
* reverting test
* test commit
* reverting test
* index unassigned
* user suggestions in right sidebar on tag page, fixes
* improving widgets a little
* line height for category
* Update tests
Co-authored-by: Ben Halpern <bendhalpern@gmail.com>
* Upgrade stripe and stripe-ruby-mock
* Replace .all with .list
* Replace .delete with .detach_source and add tests
* Fix credits spec
* Refactor StripeActiveCardsController to use Payments::Customer and fix specs
* Use the right notice to show feedback to the user
* Add UI to vomit on a user from /mod
Co-authored-by: MichaelaHunter <michaela1234@gmail.com>
* Add backend tweaks for vomitting on users
Co-authored-by: Andy Zhao <17884966+Zhao-Andy@users.noreply.github.com>
* Validate that users can't moderate articles
* Add system spec for article mod page
* Satisfy rubocop after rebase
* Fix typo and formatting
* Use reactable_id instead of user_id
Co-authored-by: Michaela Hunter <60361569+MichaelaHunter@users.noreply.github.com>
Co-authored-by: Andy Zhao <17884966+Zhao-Andy@users.noreply.github.com>
* Skip moderation notification if the user is the moderator
* Update spec/workers/notifications/moderation_notification_worker_spec.rb
Co-Authored-By: Vaidehi Joshi <vaidehi.sj@gmail.com>
Co-authored-by: Vaidehi Joshi <vaidehi.sj@gmail.com>
Because confirming a User vomit is a particularly destructive task, we
want to make it a bit more intentional. Ben recommended adding a confirm
dialog for these reports.
This commit also satisfies erblint's complaints regarding the select
element in the ransack search form.
The FAQ page displayed in production is actually generated in internal
and it might be pretty misleading to folks who want to contributing by
improving our FAQ if they find this file in the codebase.
This has the benefit of clearing up any confusing that might arise from
finding this file and also having a placeholder if someone goes the faq
route in the their dev environment.
