refactor: remove unused ErrorResponse type from summary package#103
Merged
gavinsharp merged 1 commit intomainfrom Mar 11, 2026
Merged
refactor: remove unused ErrorResponse type from summary package#103gavinsharp merged 1 commit intomainfrom
gavinsharp merged 1 commit intomainfrom
Conversation
The ErrorResponse class has been removed from the summary types package as it is no longer needed in the API. This cleanup removes unused code and simplifies the SDK structure. Key changes: - Remove ErrorResponse class from com.phenoml.api.resources.summary.types package - Clean up associated builder pattern and serialization annotations - Eliminate unused success and error field definitions 🌿 Generated with Fern
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
1 participant
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.
The
ErrorResponseclass has been removed from the summary types package. If your code referencescom.phenoml.api.resources.summary.types.ErrorResponse, you'll need to update your imports and error handling logic to use alternative error response types available in the SDK.