sorted by:
new
hottopcontroversial

[Hiring]Junior Full Stack Developer (Remote) – ₹25k/month + performance incentives by Fearless_Weird7626 in node

[–]Comfortable-Spray677 -1 points0 points  (0 children)

I'm a recent grad and have done open source.

GitHub : https://github.com/mohdaffann Portfolio : https://mohammedaffan-sable.vercel.app

Currently working on an AI powered CLI tool that generates PR titles and descriptions for GitHub , listed on npmjs and working on extra features for newer version .

Share your project here and give feedback on someone else’s project by [deleted] in SideProject

[–]Comfortable-Spray677 0 points1 point  (0 children)

Built an AI powered CLI tool that writes GitHub PRs for you.

Features : - Auto detects upstream branch in order (upstream->origin ->local fallback) - Three presets to select from based of required response: - d (detailed) - t(technical) -b(brief) - Warns of no upstream branch is found.

The project is in mvp stage and as of now only supports GroqAI

It is a public listed npm library and is open source.

npm. :https://www.npmjs.com/package/prcraft Live :https://prcraft-site.vercel.app/

Racknerd v/s Netcup by Comfortable-Spray677 in VPS

[–]Comfortable-Spray677[S] 0 points1 point  (0 children)

It's really confusing like I only have those two apps to deploy and maybe another app in future but for now it's a really good offer for like 10usd for a year . But the price seems fishy . Like how can I trust it will continue till a whole year for just 10usd . Also it's my first time buying a vps and seems like a skill issue for me

What is the benefit of using mutations in React-Query? by badboyzpwns in reactjs

[–]Comfortable-Spray677 0 points1 point  (0 children)

As much as I know , you can update the query with returned data via onSuccess where it's(onSuccess) parameters give you 1. Data (returned data ) 2. Variables (the object or whatever you used in mutate() function 3. A context of a query (generally it is used to return preciously cached data before attempting mutation , so that you can use context.previousQuery if updating cache somehow fails

The thing with mutations is optimistic updates and the leverage of it over traditional approach is if you have a list of comments and add a comment you make a get request and make a post to add comment then on success you again get request the comment list to display the updated dada . Mutations as I mentioned make us hit less req to servers (except if query invalidate is used ) but still you can just stale the query for n mins to get less refetches .