/// <summary>
/// Initializes a new instance of the <see cref="SearchResultOfTrendingEntry" /> 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 SearchResultOfTrendingEntry(List <TrendingTrendingEntry> results = default(List <TrendingTrendingEntry>), 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="GroupsV2GroupSearchResponse" /> 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 GroupsV2GroupSearchResponse(List <GroupsV2GroupV2Card> results = default(List <GroupsV2GroupV2Card>), 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="GroupsV2GetGroupsForMemberResponse" /> class.
/// </summary>
/// <param name="areAllMembershipsInactive">A convenience property that indicates if every membership this user has that is a part of this group are part of an account that is considered inactive - for example, overridden accounts in Cross Save. The key is the Group ID for the group being checked, and the value is true if the users' memberships for that group are all inactive..</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 GroupsV2GetGroupsForMemberResponse(Dictionary <string, bool> areAllMembershipsInactive = default(Dictionary <string, bool>), List <GroupsV2GroupMembership> results = default(List <GroupsV2GroupMembership>), int totalResults = default(int), bool hasMore = default(bool), QueriesPagedQuery query = default(QueriesPagedQuery), string replacementContinuationToken = default(string), bool useTotalResults = default(bool))
{
this.AreAllMembershipsInactive = areAllMembershipsInactive;
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="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="SearchResultOfGroupPotentialMembership" /> 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 SearchResultOfGroupPotentialMembership(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;
}
