You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HTTP hooks returning 4xx status codes now parse the response body and return custom error messages instead of hardcoded ones like "Invalid payload sent to hook".
This aligns HTTP hook error handling with the PostgreSQL hook dispatcher which already extracts custom errors via hookserrors.Check().
Parse non-2xx hook responses and bubble up the hook-provided
http_code/message so before_user_created rejections return the custom
error instead of “Invalid payload sent to hook” .Fixessupabase#2235.
@JEETDESAI25 thanks a lot for taking the time to work through this. Your approach was close but not exactly the behavior I was looking for so I pushed a fix in #2380
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HTTP hooks returning 4xx status codes now parse the response body and return custom error messages instead of hardcoded ones like "Invalid payload sent to hook".
This aligns HTTP hook error handling with the PostgreSQL hook dispatcher which already extracts custom errors via
hookserrors.Check().Fixes#2235.