MarseyWorld/files/routes/votes.py

307 lines
9.9 KiB
Python
Raw Normal View History

2021-10-15 14:08:27 +00:00
from files.helpers.wrappers import *
from files.helpers.get import *
2022-01-19 09:07:16 +00:00
from files.helpers.const import *
2021-10-15 14:08:27 +00:00
from files.classes import *
from flask import *
2021-10-20 23:17:53 +00:00
from files.__main__ import app, limiter, cache
2021-11-30 14:31:26 +00:00
from os import environ
2021-10-15 14:08:27 +00:00
@app.get("/votes")
2022-01-11 21:54:41 +00:00
@auth_required
2021-10-15 14:08:27 +00:00
def admin_vote_info_get(v):
link = request.values.get("link")
2022-01-14 12:04:34 +00:00
if not link: return render_template("votes.html", v=v)
2021-10-15 14:08:27 +00:00
try:
if "t2_" in link: thing = get_post(int(link.split("t2_")[1]), v=v)
elif "t3_" in link: thing = get_comment(int(link.split("t3_")[1]), v=v)
else: abort(400)
except: abort(400)
2022-03-31 14:25:49 +00:00
if thing.ghost and v.id != AEVANN_ID: abort(403)
2021-10-15 14:08:27 +00:00
2022-02-03 06:39:02 +00:00
if not thing.author:
print(thing.id, flush=True)
2022-01-21 20:56:56 +00:00
if isinstance(thing, Submission):
2022-01-06 16:46:09 +00:00
if thing.author.shadowbanned and not (v and v.admin_level):
2022-01-13 23:29:15 +00:00
thing_id = g.db.query(Submission.id).filter_by(upvotes=thing.upvotes, downvotes=thing.downvotes).order_by(Submission.id).first()[0]
2022-01-06 16:46:09 +00:00
else: thing_id = thing.id
2022-02-16 01:16:01 +00:00
ups = g.db.query(Vote).filter_by(submission_id=thing_id, vote_type=1).order_by(Vote.created_utc).all()
2021-10-15 14:08:27 +00:00
2022-02-16 01:16:01 +00:00
downs = g.db.query(Vote).filter_by(submission_id=thing_id, vote_type=-1).order_by(Vote.created_utc).all()
2021-10-15 14:08:27 +00:00
elif isinstance(thing, Comment):
2022-01-06 16:46:09 +00:00
if thing.author.shadowbanned and not (v and v.admin_level):
2022-01-13 23:29:15 +00:00
thing_id = g.db.query(Comment.id).filter_by(upvotes=thing.upvotes, downvotes=thing.downvotes).order_by(Comment.id).first()[0]
2022-01-06 16:46:09 +00:00
else: thing_id = thing.id
2022-02-16 01:16:01 +00:00
ups = g.db.query(CommentVote).filter_by(comment_id=thing_id, vote_type=1).order_by(CommentVote.created_utc).all()
2021-10-15 14:08:27 +00:00
2022-02-16 01:16:01 +00:00
downs = g.db.query(CommentVote).filter_by(comment_id=thing_id, vote_type=-1 ).order_by(CommentVote.created_utc).all()
2021-10-15 14:08:27 +00:00
if v.admin_level:
up_ids = [x[0] for x in g.db.query(CommentVote.user_id).filter_by(comment_id=thing_id, vote_type=1).order_by(CommentVote.created_utc).all()]
total_ups = g.db.query(func.sum(User.truecoins)).filter(User.id.in_(up_ids)).scalar()
total_ups = format(total_ups, ",")
patrons_ups = g.db.query(User).filter(User.id.in_(up_ids), User.patron > 0).count()
return render_template("votes.html",
v=v,
thing=thing,
ups=ups,
downs=downs,
total_ups=total_ups,
patrons_ups=patrons_ups)
2021-10-15 14:08:27 +00:00
else: abort(400)
2022-01-14 12:04:34 +00:00
return render_template("votes.html",
2021-10-15 14:08:27 +00:00
v=v,
thing=thing,
ups=ups,
2022-02-03 06:39:02 +00:00
downs=downs)
2021-10-15 14:08:27 +00:00
@app.post("/vote/post/<post_id>/<new>")
@limiter.limit("5/second;60/minute;1000/hour;2000/day")
@limiter.limit("5/second;60/minute;1000/hour;2000/day", key_func=lambda:f'{request.host}-{session.get("lo_user")}')
2022-04-20 19:25:19 +00:00
@is_not_permabanned
2021-10-15 14:08:27 +00:00
def api_vote_post(post_id, new, v):
2022-01-06 16:46:09 +00:00
if new == "-1" and environ.get('DISABLE_DOWNVOTES') == '1': return {"error": "forbidden."}, 403
2021-11-16 01:49:49 +00:00
2021-10-15 14:08:27 +00:00
if new not in ["-1", "0", "1"]: abort(400)
2021-10-26 21:10:31 +00:00
if request.headers.get("Authorization"): abort(403)
2021-10-15 14:08:27 +00:00
new = int(new)
post = get_post(post_id)
2022-01-02 00:06:46 +00:00
existing = g.db.query(Vote).filter_by(user_id=v.id, submission_id=post.id).one_or_none()
2021-10-15 14:08:27 +00:00
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
coin_delta = 1
if v.id == post.author.id:
coin_delta = 0
coin_mult = 1
if DOUBLE_XP_ENABLED > 0:
if not existing and int(time.time()) > DOUBLE_XP_ENABLED:
coin_mult = 2
elif existing and existing.created_utc > DOUBLE_XP_ENABLED:
coin_mult = 2
2021-10-15 14:08:27 +00:00
if existing and existing.vote_type == new: return "", 204
if existing:
if existing.vote_type == 0 and new != 0:
post.author.coins += coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
post.author.truecoins += coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(post.author)
existing.vote_type = new
g.db.add(existing)
elif existing.vote_type != 0 and new == 0:
post.author.coins -= coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
post.author.truecoins -= coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(post.author)
g.db.delete(existing)
else:
existing.vote_type = new
g.db.add(existing)
elif new != 0:
post.author.coins += coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
post.author.truecoins += coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(post.author)
2022-03-19 12:52:36 +00:00
2022-03-21 00:40:15 +00:00
if new == 1 and (v.agendaposter or v.shadowbanned or (v.is_banned and not v.unban_utc) or (v.profile_url.startswith('/e/') and not v.customtitle and v.namecolor == DEFAULT_COLOR)): real = False
2022-03-19 12:52:36 +00:00
else: real = True
2021-10-15 14:08:27 +00:00
vote = Vote(user_id=v.id,
vote_type=new,
submission_id=post_id,
2021-11-30 14:18:16 +00:00
app_id=v.client.application.id if v.client else None,
real = real
2021-10-15 14:08:27 +00:00
)
g.db.add(vote)
2021-10-21 20:50:00 +00:00
2022-02-16 01:42:11 +00:00
g.db.flush()
post.upvotes = g.db.query(Vote).filter_by(submission_id=post.id, vote_type=1).count()
post.downvotes = g.db.query(Vote).filter_by(submission_id=post.id, vote_type=-1).count()
post.realupvotes = g.db.query(Vote).filter_by(submission_id=post.id, real=True).count()
2022-02-16 01:42:11 +00:00
if post.author.progressivestack: post.realupvotes *= 2
g.db.add(post)
2021-10-15 14:08:27 +00:00
return "", 204
@app.post("/vote/comment/<comment_id>/<new>")
@limiter.limit("5/second;60/minute;1000/hour;2000/day")
@limiter.limit("5/second;60/minute;1000/hour;2000/day", key_func=lambda:f'{request.host}-{session.get("lo_user")}')
2022-04-20 19:25:19 +00:00
@is_not_permabanned
2021-10-15 14:08:27 +00:00
def api_vote_comment(comment_id, new, v):
2022-01-06 16:46:09 +00:00
if new == "-1" and environ.get('DISABLE_DOWNVOTES') == '1': return {"error": "forbidden."}, 403
2021-11-16 01:49:49 +00:00
2021-10-15 14:08:27 +00:00
if new not in ["-1", "0", "1"]: abort(400)
2021-10-26 21:10:31 +00:00
if request.headers.get("Authorization"): abort(403)
2021-10-15 14:08:27 +00:00
new = int(new)
try: comment_id = int(comment_id)
2022-02-04 08:59:12 +00:00
except: abort(404)
2021-10-15 14:08:27 +00:00
comment = get_comment(comment_id)
if new == 1 and comment.author_id in poll_bots: return {"error": "forbidden."}, 403
2021-12-23 15:37:12 +00:00
2022-01-02 00:06:46 +00:00
existing = g.db.query(CommentVote).filter_by(user_id=v.id, comment_id=comment.id).one_or_none()
2021-10-15 14:08:27 +00:00
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
coin_delta = 1
if v.id == comment.author_id:
coin_delta = 0
coin_mult = 1
if DOUBLE_XP_ENABLED > 0:
if not existing and int(time.time()) > DOUBLE_XP_ENABLED:
coin_mult = 2
elif existing and existing.created_utc > DOUBLE_XP_ENABLED:
coin_mult = 2
2021-10-15 14:08:27 +00:00
if existing and existing.vote_type == new: return "", 204
if existing:
if existing.vote_type == 0 and new != 0:
comment.author.coins += coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
comment.author.truecoins += coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(comment.author)
existing.vote_type = new
g.db.add(existing)
elif existing.vote_type != 0 and new == 0:
comment.author.coins -= coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
comment.author.truecoins -= coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(comment.author)
g.db.delete(existing)
else:
existing.vote_type = new
g.db.add(existing)
elif new != 0:
comment.author.coins += coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
comment.author.truecoins += coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(comment.author)
2022-03-19 12:52:36 +00:00
2022-03-21 00:40:15 +00:00
if new == 1 and (v.agendaposter or v.shadowbanned or (v.is_banned and not v.unban_utc) or (v.profile_url.startswith('/e/') and not v.customtitle and v.namecolor == DEFAULT_COLOR)): real = False
2022-03-19 12:52:36 +00:00
else: real = True
2021-10-15 14:08:27 +00:00
vote = CommentVote(user_id=v.id,
vote_type=new,
comment_id=comment_id,
2021-11-30 14:18:16 +00:00
app_id=v.client.application.id if v.client else None,
real=real
2021-10-15 14:08:27 +00:00
)
g.db.add(vote)
2022-02-16 01:42:11 +00:00
g.db.flush()
comment.upvotes = g.db.query(CommentVote).filter_by(comment_id=comment.id, vote_type=1).count()
comment.downvotes = g.db.query(CommentVote).filter_by(comment_id=comment.id, vote_type=-1).count()
comment.realupvotes = g.db.query(CommentVote).filter_by(comment_id=comment.id, real=True).count()
2022-02-16 01:42:11 +00:00
if comment.author.progressivestack: comment.realupvotes *= 2
g.db.add(comment)
2021-10-15 14:08:27 +00:00
return "", 204
@app.post("/vote/poll/<comment_id>")
2022-04-20 19:25:19 +00:00
@is_not_permabanned
2021-10-15 14:08:27 +00:00
def api_vote_poll(comment_id, v):
vote = request.values.get("vote")
if vote == "true": new = 1
elif vote == "false": new = 0
else: abort(400)
comment_id = int(comment_id)
comment = get_comment(comment_id)
2022-01-02 00:06:46 +00:00
existing = g.db.query(CommentVote).filter_by(user_id=v.id, comment_id=comment.id).one_or_none()
2021-10-15 14:08:27 +00:00
if existing and existing.vote_type == new: return "", 204
if existing:
if new == 1:
existing.vote_type = new
g.db.add(existing)
else: g.db.delete(existing)
elif new == 1:
2021-11-30 14:23:34 +00:00
vote = CommentVote(user_id=v.id, vote_type=new, comment_id=comment.id)
2021-10-15 14:08:27 +00:00
g.db.add(vote)
2022-02-16 01:42:11 +00:00
g.db.flush()
comment.upvotes = g.db.query(CommentVote).filter_by(comment_id=comment.id, vote_type=1).count()
2022-02-16 01:42:11 +00:00
g.db.add(comment)
2021-12-11 02:27:46 +00:00
return "", 204
@app.post("/bet/<comment_id>")
2022-01-15 06:31:17 +00:00
@limiter.limit("1/second;30/minute;200/hour;1000/day")
2022-05-03 02:15:35 +00:00
@limiter.limit("1/second;30/minute;200/hour;1000/day", key_func=lambda:f'{request.host}-{session.get("lo_user")}')
2022-04-20 19:25:19 +00:00
@is_not_permabanned
2021-12-11 02:27:46 +00:00
def bet(comment_id, v):
2022-05-30 12:13:11 +00:00
if not v.can_gamble: return {"error": "You have gambling disabled!"}
2021-12-11 02:27:46 +00:00
if v.coins < 200: return {"error": "You don't have 200 coins!"}
vote = request.values.get("vote")
comment_id = int(comment_id)
comment = get_comment(comment_id)
option_ids = map(lambda x: x.id, comment.post.bet_options)
existing = g.db.query(CommentVote).filter_by(user_id=v.id) \
.filter(CommentVote.comment_id.in_(option_ids)).one_or_none()
2021-12-11 02:27:46 +00:00
if existing: return "", 204
vote = CommentVote(user_id=v.id, vote_type=1, comment_id=comment.id)
g.db.add(vote)
2021-12-11 02:32:21 +00:00
2021-12-11 02:27:46 +00:00
comment.upvotes += 1
g.db.add(comment)
2021-12-11 02:32:21 +00:00
v.coins -= 200
g.db.add(v)
2022-06-24 13:19:53 +00:00
autobetter = get_account(AUTOBETTER_ID)
2021-12-11 02:32:21 +00:00
autobetter.coins += 200
g.db.add(autobetter)
2022-02-07 11:39:26 +00:00
return "", 204
@app.post("/vote/choice/<comment_id>")
2022-04-20 19:25:19 +00:00
@is_not_permabanned
2022-02-07 11:39:26 +00:00
def api_vote_choice(comment_id, v):
comment_id = int(comment_id)
comment = get_comment(comment_id)
existing = g.db.query(CommentVote).filter_by(user_id=v.id, comment_id=comment.id).one_or_none()
if existing and existing.vote_type == 1: return "", 204
if existing:
existing.vote_type = 1
g.db.add(existing)
else:
vote = CommentVote(user_id=v.id, vote_type=1, comment_id=comment.id)
g.db.add(vote)
if comment.parent_comment: parent = comment.parent_comment
else: parent = comment.post
2022-06-26 20:53:12 +00:00
vote = parent.total_choice_voted(v)
if vote:
vote.comment.upvotes = g.db.query(CommentVote).filter_by(comment_id=vote.comment.id, vote_type=1).count() - 1
2022-02-07 12:38:45 +00:00
g.db.add(vote.comment)
2022-02-07 11:39:26 +00:00
g.db.delete(vote)
2022-02-16 01:42:11 +00:00
g.db.flush()
comment.upvotes = g.db.query(CommentVote).filter_by(comment_id=comment.id, vote_type=1).count()
2022-02-16 01:42:11 +00:00
g.db.add(comment)
return "", 204