@othiagocruz That was straight forward compared to mine 😂

yeah i was wondering how to extend it yesterday but then was done for the day, slept and was thinking about what rp just did 😅

Yup! He pulled the type for the ThirdPartyApiHookContext and set it as the type for the contest parameter. - straightforward, easy and sleek

My suggestion only shines in use cases where you want to alter a property type

And that is over-engineering in this case - if you ask me

yeah i dont need this for now i was just wanting to grab the sign_up event to add the user to my database

@User in that case, you may want to add the post sign up callback in your backend code.

(and not your frontend code)

ohh that could work better yeah

did you miss that cause it was too below in the page?

i was looking at the react-auth recipe for some clues, i knew that should be somewhere in the backend also

I see. Is there anything we can do to make it clearer that the "common customisations" section is a better place to look at as opposed to the auth-react docs?

i think there are a lot of recipes that shares the same functions, so maybe group by the functions of the api? idk im really bad with documentation

i think the common denominator here is the core

and what we have access to

the other stuff are just layers i guess?

> so maybe group by the functions of the api? All recipes have slightly diff behaviour for the function.. So that would be difficult. > the other stuff are just layers i guess? Somewhat. One diff is that the backend SDK has the API logic for sign up / in etc.. Those use the functions exposed by the core's APIs.

and also, backend has means to poke the core to find out information right? like if the user is logged in and so

idk maybe a cross reference guide would help

like if youre looking for this, maybe that can help also

Yea.. session related docs are being rewritten.

its fine thats hard work really

i been on a big team once of analysts that took almost a year to write some docs that made sense

oh wow!!

I think the "common customisations" section can be embedded in "Quick Setup" in cards as a reference. Sort of what pusher did here: https://pusher.com/tutorials

the use case can be the title of these cards

Everyone looks at Quick setups - LOL 😂

hey i was testing the

handlePostSignUp

on

ThirdPartyEmailPasswordNode

, when defining it im getting this error

TypeError: Only absolute URLs are supported