[Package]: migrate ErrorBoundary component to TypeScript #446
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
raskolnikov-rodion
force-pushed
the
refactor/error-boundary-ts
branch
from
d2b779b to
d0f4402
Compare
|
At the moment, we have open work related to the ErrorBoundary component. Will close this one as duplicate |
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.
Description
Migrate the ErrorBoundary component to TypeScript.
Issue: opentargets/issues#2871
Type of change
How Has This Been Tested?
Applications were built locally. Component was imported into
StudiesPagefromuiand manually inspected in the UI.Condition: No error
Condition: With error, community view
Condition: With error, partner view
Condition: With error, dummy error message
Checklist: