Spike error recovery integration #20602
Draft
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
That's the actual feature we need, so if we can't/shouldn't upgrade we can just configure that plugin directly
chancancode
force-pushed
the
spike-error-recovery-integration
branch
3 times, most recently
from
2d8a515
to
6c41d9a
Compare
chancancode
force-pushed
the
spike-error-recovery-integration
branch
from
598e17e
to
84acfbb
Compare
6 tasks
|
For anyone looking to test this, I pushed these pre-built dist that you can point your package.json at: before: |
|
Using those branches:
|
|
Before proceeding with perf comparisons, we probably need to look in to why the error-recovery assets are 86KB more than the baseline assets |
Draft
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.
No description provided.