ForgeRock
Team
ping-javascript-sdk
Sign in / Sign up
Open main menu
ping-javascript-sdk
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
541
860aed3b chore: add changeset for journey-client error handling fix
2 days ago
by ryanbas21
r
Canceled
541
cd1f008c fix(journey-client): classify HTTP 4xx error bodies as LoginFailure RTK Query's fetchBaseQuery places HTTP error response bodies in the error slot, not data. start() and next() only destructured { data }, silently discarding AM failure bodies (e.g. 401 from social login) and returning a generic no_response_data error instead. Now extracts error.data, checks if it resembles an AM Step via isStepLike(), and routes it through createJourneyObject() so 4xx responses are properly classified as JourneyLoginFailure. Also converts resume() from throwing raw Error objects to returning typed GenericError values, maintaining the JourneyResult contract.
2 days ago
by ryanbas21
r
Previous page
Previous
Next
Next page