HookName field unavailable in the UI, thus not saved in backend. about auth HOT 7 CLOSED

Hey @deezeddd,

Thanks for the query and for raising this - the HookName is generated from the Postgres URI and used internally to invoke the hook.

A secondary consideration was that we'd eventually expose the HookName with HTTP Hooks and allow developers to edit the name of the hook so that they can correlate with events / logs. I'm not sure if we still plan to proceed with this though.

We'll either add a comment in the code or note in the docs to clarify this.

from auth.

Thanks for raising! I'll follow up with a PR either adding a comment or omitting the field entirely from serialization.

from auth.

hi @deezeddd , i can't seem to reproduce this error when i attempt to add a postgres / http hook from the dashboard - can you provide more information about how you're seeing this error message?

from auth.

Hi, there isn’t error thrown. The field hookName is available in backend which is supabase/auth but not on the frontend to edit

from auth.

@deezeddd does it impact the usability of the hook here? also, is there a reason why you need to set the hook name explicitly through the UI?

i can't remember why we made the decision not to expose it but i'll check with the team on this and get back to you

from auth.

@kangmingtay that’s what I’m confused about why it is needed at the first place when it’s not in use, this might create a confusion in long term I believe.
If there is feature that might get implemented in future then it’s not a problem.

I’ll be happy to know the reason. Thanks for letting me know.

from auth.

Thanks, @J0 and @kangmingtay for helping with the query, adding a comment will be great!
Exposing the HookName is what I thought was about to be done in future updates. Thank you for clarifying this. I will mark the issue close.

from auth.