chore: "unuse" ErrorBlock #3011
Open
Conversation
This file contains 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
Signed-off-by: John Cowen <john.cowen@konghq.com>
✅ Deploy Preview for kuma-gui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Our "ErrorBlock"/error state components aren't great:
Partly because we rarely see them, and partly (since taking a look in the component) are a little over complex and contain things they shouldn't.
Almost the entirety of the GUI no longer uses an ErrorBlock in View level components. We use
DataLoaderinstead (which embeds ErrorBlock).This PR removes the last remaining usages of ErrorBlock outside of DataLoader:
Once this is done we can pull ErrorBlock apart (and probably move it to
x/x-error-state), simplify and finally make it consistently look less broken.