stacker.news/fragments/items.js

184 lines
2.8 KiB
JavaScript
Raw Normal View History

2021-04-22 22:14:32 +00:00
import { gql } from '@apollo/client'
2021-09-30 15:46:58 +00:00
import { COMMENTS } from './comments'
2021-04-22 22:14:32 +00:00
export const ITEM_FIELDS = gql`
fragment ItemFields on Item {
id
parentId
createdAt
2023-01-12 23:53:09 +00:00
deletedAt
2021-04-22 22:14:32 +00:00
title
url
user {
2021-08-10 22:59:06 +00:00
id
2023-11-10 01:05:35 +00:00
name
optional {
streak
}
2023-09-28 20:02:25 +00:00
meMute
2021-04-22 22:14:32 +00:00
}
sub {
name
userId
moderated
2023-12-31 01:41:16 +00:00
meMuteSub
meSubscription
nsfw
}
otsHash
2023-02-04 00:08:08 +00:00
position
2021-04-22 22:14:32 +00:00
sats
Allow zapping, posting and commenting without funds or an account (#336) * Add anon zaps * Add anon comments and posts (link, discussion, poll) * Use payment hash instead of invoice id as proof of payment Our invoice IDs can be enumerated. So there is a - even though very rare - chance that an attacker could find a paid invoice which is not used yet and use it for himself. Random payment hashes prevent this. Also, since we delete invoices after use, using database IDs as proof of payments are not suitable. If a user tells us an invoice ID after we deleted it, we can no longer tell if the invoice was paid or not since the LN node only knows about payment hashes but nothing about the database IDs. * Allow pay per invoice for stackers The modal which pops up if the stacker does not have enough sats now has two options: "fund wallet" and "pay invoice" * Fix onSuccess called twice For some reason, when calling `showModal`, `useMemo` in modal.js and the code for the modal component (here: <Invoice>) is called twice. This leads to the `onSuccess` callback being called twice and one failing since the first one deletes the invoice. * Keep invoice modal open if focus is lost * Skip anon user during trust calculation * Add error handling * Skip 'invoice not found' errors * Remove duplicate insufficient funds handling * Fix insufficient funds error detection * Fix invoice amount for comments * Allow pay per invoice for bounty and job posts * Also strike on payment after short press * Fix unexpected token 'export' * Fix eslint * Remove unused id param * Fix comment copy-paste error * Rename to useInvoiceable * Fix unexpected token 'export' * Fix onConfirmation called at every render * Add invoice HMAC This prevents entities which know the invoice hash (like all LN nodes on the payment path) from using the invoice hash on SN. Only the user which created the invoice knows the HMAC and thus can use the invoice hash. * make anon posting less hidden, add anon info button explainer * Fix anon users can't zap other anon users * Always show repeat and contacts on action error * Keep track of modal stack * give anon an icon * add generic date pivot helper * make anon user's invoices expire in 5 minutes * fix forgotten find and replace * use datePivot more places * add sat amounts to invoices * reduce anon invoice expiration to 3 minutes * don't abbreviate * Fix [object Object] as error message Any errors thrown here are already objects of shape { message: string } * Fix empty invoice creation attempts I stumbled across this while checking if anons can edit their items. I monkey patched the code to make it possible (so they can see the 'edit' button) and tried to edit an item but I got this error: Variable "$amount" of required type "Int!" was not provided. I fixed this even though this function should never be called without an amount anyway. It will return a sane error in that case now. * anon func mods, e.g. inv limits * anon tips should be denormalized * remove redundant meTotalSats * correct overlay zap text for anon * exclude anon from trust graph before algo runs * remove balance limit on anon * give anon a bio and remove cowboy hat/top stackers; * make anon hat appear on profile * concat hash and hmac and call it a token * Fix localStorage cleared because error were swallowed * fix qr layout shift * restyle fund error modal * Catch invoice errors in fund error modal * invoice check backoff * anon info typo * make invoice expiration times have saner defaults * add comma to anon info * use builtin copy input label --------- Co-authored-by: ekzyis <ek@stacker.news> Co-authored-by: keyan <keyan.kousha+huumn@gmail.com>
2023-08-11 23:50:57 +00:00
meAnonSats @client
2021-04-27 21:30:58 +00:00
boost
2023-01-26 16:11:55 +00:00
bounty
2023-01-26 19:09:57 +00:00
bountyPaidTo
noteId
2022-05-17 22:09:15 +00:00
path
2023-05-06 23:17:47 +00:00
upvotes
2021-12-05 17:37:55 +00:00
meSats
meDontLikeSats
meBookmark
meSubscription
2023-08-28 14:40:29 +00:00
meForward
2022-09-22 18:44:50 +00:00
outlawed
2022-09-27 21:19:15 +00:00
freebie
2023-11-19 20:16:35 +00:00
bio
2021-04-22 22:14:32 +00:00
ncomments
2022-09-01 21:06:11 +00:00
commentSats
lastCommentAt
2022-02-17 17:23:43 +00:00
maxBid
2022-09-29 20:42:33 +00:00
isJob
2022-03-07 21:50:13 +00:00
company
location
remote
2023-05-05 17:38:56 +00:00
subName
2022-07-30 13:25:46 +00:00
pollCost
pollExpiresAt
2022-02-26 16:41:30 +00:00
status
2022-07-21 22:55:05 +00:00
uploadId
2021-11-27 18:01:02 +00:00
mine
2023-10-01 23:03:52 +00:00
imgproxyUrls
2023-02-04 00:08:08 +00:00
}`
export const ITEM_FULL_FIELDS = gql`
${ITEM_FIELDS}
fragment ItemFullFields on Item {
...ItemFields
text
2021-07-08 00:15:27 +00:00
root {
id
title
2023-02-04 00:08:08 +00:00
bounty
bountyPaidTo
2023-05-05 17:38:56 +00:00
subName
2021-10-27 18:26:34 +00:00
user {
id
2023-11-10 01:05:35 +00:00
name
optional {
streak
}
2021-10-27 18:26:34 +00:00
}
sub {
name
userId
moderated
2023-12-31 01:41:16 +00:00
meMuteSub
meSubscription
}
2021-07-08 00:15:27 +00:00
}
multiple forwards on a post (#403) * multiple forwards on a post first phase of the multi-forward support * update the graphql mutation for discussion posts to accept and validate multiple forwards * update the discussion form to allow multiple forwards in the UI * start working on db schema changes * uncomment db schema, add migration to create the new model, and update create_item, update_item stored procedures * Propagate updates from discussion to poll, link, and bounty forms Update the create, update poll sql functions for multi forward support * Update gql, typedefs, and resolver to return forwarded users in items responses * UI changes to show multiple forward recipients, and conditional upvote logic changes * Update notification text to reflect multiple forwards upon vote action * Disallow duplicate stacker entries * reduce duplication in populating adv-post-form initial values * Update item_act sql function to implement multi-way forwarding * Update referral functions to scale referral bonuses for forwarded users * Update notification text to reflect non-100% forwarded sats cases * Update wallet history sql queries to accommodate multi-forward use cases * Block zaps for posts you are forwarded zaps at the API layer, in addition to in the UI * Delete fwdUserId column from Item table as part of migration * Fix how we calculate stacked sats after partial forwards in wallet history * Exclude entries from wallet history that are 0 stacked sats from posts with 100% forwarded to other users * Fix wallet history query for forwarded stacked sats to be scaled by the fwd pct * Reduce duplication in adv post form, and do some style tweaks for better layout * Use MAX_FORWARDS constants * Address various PR feedback * first enhancement pass * enhancement pass too --------- Co-authored-by: keyan <keyan.kousha+huumn@gmail.com> Co-authored-by: Keyan <34140557+huumn@users.noreply.github.com>
2023-08-23 22:44:17 +00:00
forwards {
userId
pct
user {
name
}
}
2021-04-22 22:14:32 +00:00
}`
2023-01-22 20:17:50 +00:00
export const ITEM_OTS_FIELDS = gql`
fragment ItemOtsFields on Item {
id
title
text
url
parentOtsHash
otsHash
deletedAt
}`
export const ITEM_OTS = gql`
${ITEM_OTS_FIELDS}
query Item($id: ID!) {
item(id: $id) {
...ItemOtsFields
}
}`
2022-08-18 18:15:24 +00:00
export const POLL_FIELDS = gql`
fragment PollFields on Item {
poll {
meVoted
count
options {
id
option
count
meVoted
}
}
}`
2021-10-26 20:49:37 +00:00
export const ITEM = gql`
2023-02-04 00:08:08 +00:00
${ITEM_FULL_FIELDS}
2022-08-18 18:15:24 +00:00
${POLL_FIELDS}
2021-10-26 20:49:37 +00:00
query Item($id: ID!) {
item(id: $id) {
2023-02-04 00:08:08 +00:00
...ItemFullFields
2022-08-18 18:15:24 +00:00
...PollFields
2021-10-26 20:49:37 +00:00
}
}`
2021-06-22 17:47:49 +00:00
2021-10-26 20:49:37 +00:00
export const ITEM_FULL = gql`
2023-02-04 00:08:08 +00:00
${ITEM_FULL_FIELDS}
2022-08-18 18:15:24 +00:00
${POLL_FIELDS}
2021-09-30 15:46:58 +00:00
${COMMENTS}
2023-07-26 00:45:35 +00:00
query Item($id: ID!, $sort: String) {
2021-10-26 20:49:37 +00:00
item(id: $id) {
2023-02-04 00:08:08 +00:00
...ItemFullFields
prior
2022-08-18 18:15:24 +00:00
...PollFields
2023-07-26 00:45:35 +00:00
comments(sort: $sort) {
2021-09-30 15:46:58 +00:00
...CommentsRecursive
}
2021-04-22 22:14:32 +00:00
}
}`
2021-04-24 21:05:07 +00:00
2022-10-26 22:46:01 +00:00
export const RELATED_ITEMS = gql`
${ITEM_FIELDS}
2023-11-22 16:30:43 +00:00
query Related($title: String, $id: ID, $cursor: String, $limit: Limit) {
2022-10-26 22:46:01 +00:00
related(title: $title, id: $id, cursor: $cursor, limit: $limit) {
cursor
items {
...ItemFields
}
}
}
`
export const RELATED_ITEMS_WITH_ITEM = gql`
${ITEM_FIELDS}
2023-11-22 16:30:43 +00:00
query Related($title: String, $id: ID!, $cursor: String, $limit: Limit) {
2022-10-26 22:46:01 +00:00
item(id: $id) {
...ItemFields
}
related(title: $title, id: $id, cursor: $cursor, limit: $limit) {
cursor
items {
...ItemFields
}
}
}
`