Repository navigation
feat(error-content): Show errors in plain language with the raw text kept - #313
Merged
Merged
Conversation
yahyafakhroji
requested review from
gaghan430,
kevwilliams and
mattdjenkinson
November 18, 2026 14:20
scotwells
approved these changes
Nov 18, 2026
datum-ui showed errors raw or not at all: a failed DataTable.Server load read "No results." with no way to retry, and each portal would have had to build plain-English errors on its own. A new error-content entry point adds describeApiError, which turns common Kubernetes errors into a plain headline and keeps the raw text, ErrorContent to show it with a collapsed Error details section, and ErrorDescriptionProvider so an app can change the wording or name product areas. Server tables now show the error with Retry through a new refetch(), and errorContent lets an app replace it.
TaskQueue's summary showed whatever a processor threw, and Dropzone passed react-dropzone's developer text for only the first rejected file. TaskQueue now describes thrown errors, for a whole task or one item, with the app's error describer or a formatError option, and shows the raw text under Error details. Text passed to ctx.fail stays as written. Dropzone explains each rejected file in a sentence, passes them all to onError and adds onReject.
yahyafakhroji
marked this pull request as draft
November 18, 2026 14:40
yahyafakhroji
force-pushed
the
feat/plain-language-errors
branch
from
November 18, 2026 14:40
96427d7 to
05c030e
Compare
yahyafakhroji
marked this pull request as ready for review
November 18, 2026 14:40
5 tasks
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
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.
Problem
datum-ui showed errors raw or not at all. A failed
DataTable.Serverload read "No results." with no way to retry. TaskQueue's summary showed raw Kubernetes errors such as permission denials. Dropzone passed react-dropzone's developer text, and only for the first rejected file. Each portal would have had to build #722's plain-English errors on its own.Solution
A new
@datum-cloud/datum-ui/error-contententry point addsdescribeApiError, which turns common Kubernetes errors into a plain headline and keeps the raw text. It also adds anErrorContentcomponent that shows the error with a collapsed "Error details", andErrorDescriptionProviderso an app can change the wording or name product areas. Server tables now show the error with Retry through a newrefetch(). TaskQueue translates thrown errors and shows the raw text in its summary. Dropzone explains each rejected file. Cloud-portal's table wrapper keeps rendering its own error, and messages already written for people keep their wording.Closes #311
Ref: datum-cloud/enhancements#722