feat(error-handling): Fix production errors and improve error resilience #953
Conversation
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
|
🚀 Preview Deployment: View Here |
APP-270: Add errorUtils.serialize() to safely serialize errors without circular references APP-389: Add missing 'use client' directives to components using hooks (partial fix) APP-461: Add useSafeTranslations() hook with fallback for error boundaries APP-453: Handle 404 responses directly in AragonBackendServiceError to avoid JSON parse errors APP-463: Skip plugins-by-dao and policies API calls on v2 (endpoints not deployed to production)
tyhonchik
force-pushed
the
fix-sentry-errors-jan-26
branch
from
142396d to
780469e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
APP-270: Add errorUtils.serialize() to safely serialize errors without circular references
APP-389: Add missing 'use client' directives to components using hooks (partial fix)
APP-461: Add useSafeTranslations() hook with fallback for error boundaries
APP-453: Handle 404 responses directly in AragonBackendServiceError to avoid JSON parse errors
APP-463: Skip plugins-by-dao and policies API calls on v2 (endpoints not deployed to production)
Description
Fix multiple production errors related to error handling, hydration, and API compatibility.
Converting circular structure to JSON- errors containing DOM references crashed JSON.stringifyuseTranslations must be used within Provider- error boundaries crashed outside provider contextSyntaxError: Unexpected token- 404 responses with plain text "Not Found" failed JSON parsingError parsing response (status=404)- v3-only endpoints called on v2 productionNotes
DateFormat.RELATIVEmay still cause mismatches due to SSR/client time differencesType of Change
Developer Checklist:
Review Checklist: