Repository navigation
feat: remove AggregationGetRequest class - #16
Closed
fern-api[bot] wants to merge 1 commit into
Closed
fern-api[bot] wants to merge 1 commit into
fern-api[bot] wants to merge 1 commit into
Conversation
Remove the AggregationGetRequest class from the aggregation package. This class was used to structure parameters for aggregation API requests but is no longer needed in the updated SDK architecture. Key changes: - Removed AggregationGetRequest class with all 45+ query parameters - Removed associated builder pattern implementation - Removed JSON serialization annotations and field mappings 🌿 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
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.
AggregationGetRequestclass has been removed from the aggregation package. If your code references this class directly, you will need to update your implementation to use the new aggregation API structure.LatestheadlinesClientandSearchLinkClientclasses are no longer available, along with various request parameter enum types likeAggregationGetRequestSortBy,SearchGetRequestClusteringVariable, and others. Applications using these removed classes should migrate to the consolidated client implementations available in other SDK modules.AsyncSearchsimilarClientclass and all its methods (get(),post()) are no longer available. Applications using these APIs must remove all references to search similar functionality.SearchsimilarClientclass and itsget()andpost()methods are no longer available. Applications using these methods will need to remove those calls or implement alternative search functionality.SearchSimilarGetRequestclass has been removed from the SDK. Code that previously used this class for similar document searches will need to be updated to use alternative search methods.SearchSimilarGetResponse,SearchSimilarPostResponse,SearchSimilarResponseDto,FailedSearchSimilarResponseDtoclasses and related types are no longer available. Applications using these types should migrate to alternative search methods provided by the API.SimilarArticleEntityclass has been removed from the SDK. If your code references this class, you will need to update it to use alternative article entity types or remove the functionality that depends on similar article data.SimilarDocumentclass has been removed. Code using this type will need to be updated to use alternative document representations. Thelatestheadlines()method has been renamed tolatestHeadlines(), and the separatesearchLink()andsearchsimilar()methods have been consolidated into a singlesearchByLink()method.get()is nowcountGet()andpost()is nowcountPost(). Update your code to use the new method names. New SSE streaming support added for handling discriminated union types in Server-Sent Events.get()andpost()tocountGet()andcountPost()respectively. Additionally, the corresponding request and response classes have been renamed to include "Count" in their names (e.g.,AggregationPostRequestis nowAggregationCountPostRequest). Existing code using these methods will need to be updated to use the new method names and class names.allLinksTextparameter added toAuthorsPostRequestfor enhanced content filtering. Thetheme,notTheme, andpublishedDatePrecisionparameters now accept String values for improved flexibility. Additional method overloads available for breaking news operations that acceptRequestOptions.robotsCompliantfield has been removed fromBreakingNewsGetRequestandBreakingNewsPostRequest. ThethemeandnotThemefields inBreakingNewsPostRequestnow accept String values instead of enum types. ThesortByfield inBreakingNewsGetRequestnow uses the sharedSortBytype instead ofBreakingNewsGetRequestSortBy.contentfield inArticleEntityis now optional (Optional<String>instead ofString). Existing code that directly accessesgetContent()will need to handle the Optional wrapper. The class no longer implementsIArticleEntityinterface, so code that depends on this interface will need to be updated.ThemeandNotThemetypes have been renamed toArticleEntityAuthorsandArticleEntityJournalistsrespectively. Existing code using these types will need to update import statements and class references to use the new names.contentfield inBreakingNewsArticleEntityis now optional and returnsOptional<String>instead ofString. Code that previously accessed.getContent()directly must now handle the Optional wrapper (e.g.,.getContent().orElse("")). TherobotsCompliantfield has been removed from the public API. Theauthorsandjournalistsfields now use entity-specific types (BreakingNewsArticleEntityAuthorsandBreakingNewsArticleEntityJournalists) instead of the genericAuthorsandJournaliststypes.LogConfiginterface. Use thelogging()method on client builders to configure debug output for HTTP requests and responses. RequestOptions now accepts query parameters for all endpoints, and search endpoints support the newall_links_textparameter.AggregationCountGetRequestclass available for news aggregation with comprehensive filtering options including language preferences, geographic targeting, content classification, sentiment analysis, and entity-based filtering.additionalProperty()andadditionalProperties()are now available on SourceInfo, SubscriptionResponseDto, and TimeFrameCount for handling additional API response fields.