fix: another TS SDK error handling tweak #873
Merged
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
…again # Conflicts: # packages/api-explorer/src/components/SideNav/SideNav.spec.tsx # packages/api-explorer/src/components/SideNav/SideNav.tsx # packages/api-explorer/src/components/SideNav/searchUtils.ts # packages/api-explorer/src/reducers/search/reducer.spec.ts
APIX Tests 1 files ±0 77 suites ±0 2m 35s ⏱️ -34s For more details on these failures, see this check. Results for commit b7917ec. ± Comparison against base commit bff67d4. |
Codegen Tests 1 files 6 suites 24s ⏱️ Results for commit 85d50d4. |
Typescript Tests 6 files 75 suites 4m 9s ⏱️ Results for commit 85d50d4. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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.
Some dependency changes broke low-level error handling for
@looker/sdk-rtlin some scenarios. This hopefully fixes the various ways and means of processing the error condition