OrJDev

OSS and @solid_js

[OrJDev @OrJDevv]

SSO with @authjs and @solid_js

https://t.co/hOANuRb2qx

Thanks @AtilaFassina for this video

[Dev Agrawal @devagrawal09]

Introducing: Solid-Socket

Building Realtime Apps Is Easy Again!

Just mark a file with "use socket", and write your code just like a regular client-side app

(#SolidHack 2024 entry, please vote!)

[goosewin @Goosewin]

hackathons

[OrJDev @OrJDevv]

Meh how can such a big product like Pusher not support basic necessities in WS.

[OrJDev @OrJDevv]

Is there anyone from @pusher that can answer a question? Or if is anyone familiar with it

[OrJDev @OrJDevv]

@Mr_Chonky @TkDodo @aryan__deora That’s the issue, I can’t have it thrown during ssr haha otherwise i wouldn’t have even tweeted that. I need to set the error state without throwing the actual error. Solid query currently doesn’t handle errors thrown during ssr and it causes the state to freeze

[OrJDev @OrJDevv]

@TkDodo is there a way i could return an error via a query function rather than throwing it.

queryClient.setError(…)

Or

createQuery(()=> queryError(new Error(…));

The reason being, i have an app in production using Solid Query, however there is a bug when throwing on ssr

[OrJDev @OrJDevv]

@TkDodo @aryan__deora This is my query

const q = createQuery(()=> {
return {
queryFn: ()=> {
try {
throw Error(…)
} catch {
// how do i set q.error to he this error
}
}
})

[OrJDev @OrJDevv]

@TkDodo @aryan__deora I need a way to actually set the error state without it being thrown (during ssr solid query currently does not handle errors correctly).

So assuming i have a query function, what is the best way to set the error state on it considering the function provided does not throw

[OrJDev @OrJDevv]

@TkDodo So if i do that, what should i return to the query function. Can i return

new Error(..)

I assume that won’t be cached correctly if i do that?

[OrJDev @OrJDevv]

I think queryError is a better approach tho and shouldn’t be hard to implement either, its just handling both queryError in addition to throws in the same way

[OrJDev @OrJDevv]

https://t.co/NvD4H8rmJm

[OrJDev @OrJDevv]

I think you meant your favorite server actions lib (pRPC). (Jk vote for all three)

[Brenley Dueck @brenelz]

Excuse me?! I think you mean your favorite is Solid Issue Tracker Lite. (jk vote for both) https://t.co/AzqMmePBCq

[OrJDev @OrJDevv]

Votes for the 2024 @solid_js Hackathon are now live.

https://t.co/G5qon0vKBP

I made 2 submissions (2 different categories).

Best SolidStart App:
https://t.co/ngIFaG3ltC

Best Ecosystem Utility:
https://t.co/bMg70Wal98

[OrJDev @OrJDevv]

@balazsorban44 Awesome its working. Thanks

[OrJDev @OrJDevv]

@balazsorban44 @authjs

Meh, your gh issues automatically close my issues due to lack of information so i will just @ you here to lyk

https://t.co/TGtDpUqF5E

[OrJDev @OrJDevv]

@pusher how do i update a watchlist without re-authenticating the user?

We first get initial watchlist on page loads
Then i want to add a new id to the watchlist after certain action

[OrJDev @OrJDevv]

@jullerino @TkDodo Sure will do

[OrJDev @OrJDevv]

@jullerino @TkDodo Having this in addition to the current api is great, so devs can choose the api they want - and still having all the features you mentioned in the RFC, or stick to the old one because they don’t notice the issues you mentioned on daily basis

[OrJDev @OrJDevv]

@jullerino @TkDodo IMO, this feels like going back in time. I think tRPC is an amazing project that changed how we write code nowadays, but the reasons you mentioned doesn’t justify to make the api worse (not actually bad but compared to where we got now).
Having this in addition is great