/// <summary>
/// Initializes a new instance of the <see cref="ForumPostSearchResponse" /> class.
/// </summary>
/// <param name="RelatedPosts">RelatedPosts.</param>
/// <param name="Authors">Authors.</param>
/// <param name="Groups">Groups.</param>
/// <param name="SearchedTags">SearchedTags.</param>
/// <param name="Polls">Polls.</param>
/// <param name="RecruitmentDetails">RecruitmentDetails.</param>
/// <param name="AvailablePages">AvailablePages.</param>
/// <param name="Results">Results.</param>
/// <param name="TotalResults">TotalResults.</param>
/// <param name="HasMore">HasMore.</param>
/// <param name="Query">Query.</param>
/// <param name="ReplacementContinuationToken">ReplacementContinuationToken.</param>
/// <param name="UseTotalResults">If useTotalResults is true, then totalResults represents an accurate count. If False, it does not, and may be estimated/only the size of the current page. Either way, you should probably always only trust hasMore. This is a long-held historical throwback to when we used to do paging with known total results. Those queries toasted our database, and we were left to hastily alter our endpoints and create backward- compatible shims, of which useTotalResults is one..</param>
public ForumPostSearchResponse(List <ForumPostResponse> RelatedPosts = default(List <ForumPostResponse>), List <UserGeneralUser> Authors = default(List <UserGeneralUser>), List <GroupsV2GroupResponse> Groups = default(List <GroupsV2GroupResponse>), List <TagsModelsContractsTagResponse> SearchedTags = default(List <TagsModelsContractsTagResponse>), List <ForumPollResponse> Polls = default(List <ForumPollResponse>), List <ForumForumRecruitmentDetail> RecruitmentDetails = default(List <ForumForumRecruitmentDetail>), int?AvailablePages = default(int?), List <ForumPostResponse> Results = default(List <ForumPostResponse>), int?TotalResults = default(int?), bool?HasMore = default(bool?), QueriesPagedQuery Query = default(QueriesPagedQuery), string ReplacementContinuationToken = default(string), bool?UseTotalResults = default(bool?))
{
this.RelatedPosts = RelatedPosts;
this.Authors = Authors;
this.Groups = Groups;
this.SearchedTags = SearchedTags;
this.Polls = Polls;
this.RecruitmentDetails = RecruitmentDetails;
this.AvailablePages = AvailablePages;
this.Results = Results;
this.TotalResults = TotalResults;
this.HasMore = HasMore;
this.Query = Query;
this.ReplacementContinuationToken = ReplacementContinuationToken;
this.UseTotalResults = UseTotalResults;
}
/// <summary>
/// Initializes a new instance of the <see cref="QueriesSearchResult" /> class.
/// </summary>
/// <param name="TotalResults">TotalResults.</param>
/// <param name="HasMore">HasMore.</param>
/// <param name="Query">Query.</param>
/// <param name="ReplacementContinuationToken">ReplacementContinuationToken.</param>
/// <param name="UseTotalResults">If useTotalResults is true, then totalResults represents an accurate count. If False, it does not, and may be estimated/only the size of the current page. Either way, you should probably always only trust hasMore. This is a long-held historical throwback to when we used to do paging with known total results. Those queries toasted our database, and we were left to hastily alter our endpoints and create backward- compatible shims, of which useTotalResults is one..</param>
public QueriesSearchResult(int?TotalResults = default(int?), bool?HasMore = default(bool?), QueriesPagedQuery Query = default(QueriesPagedQuery), string ReplacementContinuationToken = default(string), bool?UseTotalResults = default(bool?))
{
this.TotalResults = TotalResults;
this.HasMore = HasMore;
this.Query = Query;
this.ReplacementContinuationToken = ReplacementContinuationToken;
this.UseTotalResults = UseTotalResults;
}
/// <summary>
/// Initializes a new instance of the <see cref="SearchResultOfCommunityLiveStatus" /> class.
/// </summary>
/// <param name="Results">Results.</param>
/// <param name="TotalResults">TotalResults.</param>
/// <param name="HasMore">HasMore.</param>
/// <param name="Query">Query.</param>
/// <param name="ReplacementContinuationToken">ReplacementContinuationToken.</param>
/// <param name="UseTotalResults">If useTotalResults is true, then totalResults represents an accurate count. If False, it does not, and may be estimated/only the size of the current page. Either way, you should probably always only trust hasMore. This is a long-held historical throwback to when we used to do paging with known total results. Those queries toasted our database, and we were left to hastily alter our endpoints and create backward- compatible shims, of which useTotalResults is one..</param>
public SearchResultOfCommunityLiveStatus(List <CommunityCommunityLiveStatus> Results = default(List <CommunityCommunityLiveStatus>), int?TotalResults = default(int?), bool?HasMore = default(bool?), QueriesPagedQuery Query = default(QueriesPagedQuery), string ReplacementContinuationToken = default(string), bool?UseTotalResults = default(bool?))
{
this.Results = Results;
this.TotalResults = TotalResults;
this.HasMore = HasMore;
this.Query = Query;
this.ReplacementContinuationToken = ReplacementContinuationToken;
this.UseTotalResults = UseTotalResults;
}
/// <summary>
/// Initializes a new instance of the <see cref="SearchResultOfDestinyEntitySearchResultItem" /> class.
/// </summary>
/// <param name="Results">Results.</param>
/// <param name="TotalResults">TotalResults.</param>
/// <param name="HasMore">HasMore.</param>
/// <param name="Query">Query.</param>
/// <param name="ReplacementContinuationToken">ReplacementContinuationToken.</param>
/// <param name="UseTotalResults">If useTotalResults is true, then totalResults represents an accurate count. If False, it does not, and may be estimated/only the size of the current page. Either way, you should probably always only trust hasMore. This is a long-held historical throwback to when we used to do paging with known total results. Those queries toasted our database, and we were left to hastily alter our endpoints and create backward- compatible shims, of which useTotalResults is one..</param>
public SearchResultOfDestinyEntitySearchResultItem(List <DestinyDefinitionsDestinyEntitySearchResultItem> Results = default(List <DestinyDefinitionsDestinyEntitySearchResultItem>), int?TotalResults = default(int?), bool?HasMore = default(bool?), QueriesPagedQuery Query = default(QueriesPagedQuery), string ReplacementContinuationToken = default(string), bool?UseTotalResults = default(bool?))
{
this.Results = Results;
this.TotalResults = TotalResults;
this.HasMore = HasMore;
this.Query = Query;
this.ReplacementContinuationToken = ReplacementContinuationToken;
this.UseTotalResults = UseTotalResults;
}
/// <summary>
/// Initializes a new instance of the <see cref="GroupsV2GroupPotentialMembershipSearchResponse" /> class.
/// </summary>
/// <param name="Results">Results.</param>
/// <param name="TotalResults">TotalResults.</param>
/// <param name="HasMore">HasMore.</param>
/// <param name="Query">Query.</param>
/// <param name="ReplacementContinuationToken">ReplacementContinuationToken.</param>
/// <param name="UseTotalResults">If useTotalResults is true, then totalResults represents an accurate count. If False, it does not, and may be estimated/only the size of the current page. Either way, you should probably always only trust hasMore. This is a long-held historical throwback to when we used to do paging with known total results. Those queries toasted our database, and we were left to hastily alter our endpoints and create backward- compatible shims, of which useTotalResults is one..</param>
public GroupsV2GroupPotentialMembershipSearchResponse(List <GroupsV2GroupPotentialMembership> Results = default(List <GroupsV2GroupPotentialMembership>), int?TotalResults = default(int?), bool?HasMore = default(bool?), QueriesPagedQuery Query = default(QueriesPagedQuery), string ReplacementContinuationToken = default(string), bool?UseTotalResults = default(bool?))
{
this.Results = Results;
this.TotalResults = TotalResults;
this.HasMore = HasMore;
this.Query = Query;
this.ReplacementContinuationToken = ReplacementContinuationToken;
this.UseTotalResults = UseTotalResults;
}
/// <summary>
/// Initializes a new instance of the <see cref="SearchResultOfPostResponse" /> class.
/// </summary>
/// <param name="Results">Results.</param>
/// <param name="TotalResults">TotalResults.</param>
/// <param name="HasMore">HasMore.</param>
/// <param name="Query">Query.</param>
/// <param name="ReplacementContinuationToken">ReplacementContinuationToken.</param>
/// <param name="UseTotalResults">If useTotalResults is true, then totalResults represents an accurate count. If False, it does not, and may be estimated/only the size of the current page. Either way, you should probably always only trust hasMore. This is a long-held historical throwback to when we used to do paging with known total results. Those queries toasted our database, and we were left to hastily alter our endpoints and create backward- compatible shims, of which useTotalResults is one..</param>
public SearchResultOfPostResponse(List <ForumPostResponse> Results = default(List <ForumPostResponse>), int?TotalResults = default(int?), bool?HasMore = default(bool?), QueriesPagedQuery Query = default(QueriesPagedQuery), string ReplacementContinuationToken = default(string), bool?UseTotalResults = default(bool?))
{
this.Results = Results;
this.TotalResults = TotalResults;
this.HasMore = HasMore;
this.Query = Query;
this.ReplacementContinuationToken = ReplacementContinuationToken;
this.UseTotalResults = UseTotalResults;
}
/// <summary>
/// Initializes a new instance of the <see cref="SearchResultOfGroupMemberApplication" /> class.
/// </summary>
/// <param name="Results">Results.</param>
/// <param name="TotalResults">TotalResults.</param>
/// <param name="HasMore">HasMore.</param>
/// <param name="Query">Query.</param>
/// <param name="ReplacementContinuationToken">ReplacementContinuationToken.</param>
/// <param name="UseTotalResults">If useTotalResults is true, then totalResults represents an accurate count. If False, it does not, and may be estimated/only the size of the current page. Either way, you should probably always only trust hasMore. This is a long-held historical throwback to when we used to do paging with known total results. Those queries toasted our database, and we were left to hastily alter our endpoints and create backward- compatible shims, of which useTotalResults is one..</param>
public SearchResultOfGroupMemberApplication(List <GroupsV2GroupMemberApplication> Results = default(List <GroupsV2GroupMemberApplication>), int?TotalResults = default(int?), bool?HasMore = default(bool?), QueriesPagedQuery Query = default(QueriesPagedQuery), string ReplacementContinuationToken = default(string), bool?UseTotalResults = default(bool?))
{
this.Results = Results;
this.TotalResults = TotalResults;
this.HasMore = HasMore;
this.Query = Query;
this.ReplacementContinuationToken = ReplacementContinuationToken;
this.UseTotalResults = UseTotalResults;
}
