I just received a notification that the new version of login/post login is updated. I try to use it to replace the legacy action which I created before.
But it seems the event data is not exactly the same.
For example, we have multiples sites with the same auth0 talent. We are using event.actor.query.redirect_uri to detect where is the request come from. Then we will do different action for different site’s request.
But we lose this data in new login/post login action. As I know the only change here should be the params of API. Could we keep the event as the same as before?
I have asked the team that has built Actions about how to access the data that used to be available in the event.actor object during beta and will let you know what I hear back!
I’ve heard back from the team, and they let me know that the event.actor data is now split between event.transaction and event.request. The redirect_uri is not currently available, but the team is working on adding it now and it will be available very soon. Thank you for this feedback!
The version of Node in the current runtime doesn’t yet support optional chaining. We’ve decided not to do any source-to-source transformation for the time being either.
As newer Node runtimes with optional chaining get rolled out in Actions, this syntax will be supported.