-
Notifications
You must be signed in to change notification settings - Fork 33
Conversation
Have opened it up for review. Do we need to create new notification settings in jwt for tip posts. Isn't new_proposal sufficient? |
Sure I'll take a look. |
You're right, no need to be too granular, new proposals does the job. One quick thing I see right away from your screenshot, the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow that's a big one! I tried to play with it, but stopped when I realized my hasura was failing over and over because the remote schema didn't contain tip. I guess you're still using 4466 in your docker-compose, for HASURA_CHAIN_DB_REMOTE_SCHEMA
, whereas you should have http://localhost:4000, like in test and prod. And this brings us to the fact that the open-server needs new resolver to cater for the new tips (I forgot about it in the issue, just added it).
I went briefly through the code, catching small things here and there. I'll review everything again thoroughly once again and play with it. I checked briefly the input code, couldn't spot any problem at first glance, I'll leave that for my next review as well, when things are running end to end.
Co-authored-by: Thibaut Sardan <[email protected]>
Co-authored-by: Thibaut Sardan <[email protected]>
* squash and migrate to v2 * remove useless users mention * remove first useless proposals table creation * delete consecutive add drop column proposal_id * delete consecutive add drop creation and modification_date * delete consecutive add drop on reply * delete consecutive add drop on public.reactions * delete consecutive add drop on public.post_votes * delete consecutive add drop on public.post.poll_id and public.post.has_poll * delete consecutive add drop updated at public.poll and poll_votes * fix tons of nits to make migration sucessful * fix wrong uppercase * remove auto-migration (not-working) and update readme * delete migration_backup and add cron_triggers.yaml
Fixed with ugly hack for now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple comments to make sure we stay consistent on the node-watcher side to prevent bugs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small nits here and there, I'll commit them. I want to test the tip endorsement on a new node, which I haven't done yet, and then it should be good to go.
Co-authored-by: Thibaut Sardan <[email protected]>
Co-authored-by: Thibaut Sardan <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 🎉 🎉
working well on 0.8.14.
We've added some hacks, but it's a VERY complete, thank you so much for all this work.
* Added tip schema * Tip being added to prisma * added chain db watcher and frontend * Added tip proposal * Added Tip to frontend * Added tip section * Added finder * Added chain db watcher for tip * remove who * Added types in refetch * Added endorse sidebar * Added tip type for new proposal emai; * fix * Update chain-db-watcher/README.md Co-authored-by: Thibaut Sardan <[email protected]> * Update chain-db-watcher/README.md Co-authored-by: Thibaut Sardan <[email protected]> * chain db open serve modifications for tip * removed endorsements * removed datamodel * yarn generate * removed endorsements * fix * fix * sidebar component * fix * removed code * fix graphql codegen * correct tip reason * allow numbers * Added time to block * added status update for tips * create tip status * showing only opened status * codegen * fix * added tip closes * fix finder * show only open ones * Hasura migration to v2 and squash (paritytech#950) * squash and migrate to v2 * remove useless users mention * remove first useless proposals table creation * delete consecutive add drop column proposal_id * delete consecutive add drop creation and modification_date * delete consecutive add drop on reply * delete consecutive add drop on public.reactions * delete consecutive add drop on public.post_votes * delete consecutive add drop on public.post.poll_id and public.post.has_poll * delete consecutive add drop updated at public.poll and poll_votes * fix tons of nits to make migration sucessful * fix wrong uppercase * remove auto-migration (not-working) and update readme * delete migration_backup and add cron_triggers.yaml * ugly hack * proper closing and closed display * Added check for closing * added more check * fix * fix * Change status name * tip openend * Update chain-db-watcher/src/sync/index.ts Co-authored-by: Thibaut Sardan <[email protected]> * Update chain-db-watcher/src/sync/queries/chain-db.queries.ts Co-authored-by: Thibaut Sardan <[email protected]> * Update front-end/src/screens/Tips/index.tsx * Update front-end/src/screens/Tips/index.tsx * Update front-end/src/components/Listings/TipListing.tsx * Update front-end/src/screens/Tips/index.tsx * Update chain-db-watcher/src/queries.ts * closing shouldnot show negative days Co-authored-by: Thibaut Sardan <[email protected]> Co-authored-by: thib <[email protected]> Co-authored-by: Nikhil Ranjan <[email protected]>
Closes: #914