@microsoft/msgraph-sdk-teams
Version:
Teams fluent API for Microsoft Graph
109 lines • 5.87 kB
TypeScript
import { type ConversationMember, type ConversationMemberCollectionResponse } from '@microsoft/msgraph-sdk/models/index.js';
import { type AddRequestBuilder } from './add/index.js';
import { type CountRequestBuilder } from './count/index.js';
import { type ConversationMemberItemRequestBuilder } from './item/index.js';
import { type RemoveRequestBuilder } from './remove/index.js';
import { type BaseRequestBuilder, type KeysToExcludeForNavigationMetadata, type NavigationMetadata, type RequestConfiguration, type RequestInformation, type RequestsMetadata } from '@microsoft/kiota-abstractions';
/**
* Provides operations to manage the members property of the microsoft.graph.team entity.
*/
export interface MembersRequestBuilder extends BaseRequestBuilder<MembersRequestBuilder> {
/**
* Provides operations to call the add method.
*/
get add(): AddRequestBuilder;
/**
* Provides operations to count the resources in the collection.
*/
get count(): CountRequestBuilder;
/**
* Provides operations to call the remove method.
*/
get remove(): RemoveRequestBuilder;
/**
* Provides operations to manage the members property of the microsoft.graph.team entity.
* @param conversationMemberId The unique identifier of conversationMember
* @returns {ConversationMemberItemRequestBuilder}
*/
byConversationMemberId(conversationMemberId: string): ConversationMemberItemRequestBuilder;
/**
* Get the conversationMember collection of a team. The membership IDs returned by the server must be treated as opaque strings. The client shouldn't try to parse or make assumptions about these resource IDs. In the future, membership results can include users from various tenants, as indicated in the response. Clients should avoid assuming that all members exclusively belong to the current tenant.
* @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
* @returns {Promise<ConversationMemberCollectionResponse>}
* @throws {ODataError} error when the service returns a 4XX or 5XX status code
* @see {@link https://learn.microsoft.com/graph/api/team-list-members?view=graph-rest-1.0|Find more info here}
*/
get(requestConfiguration?: RequestConfiguration<MembersRequestBuilderGetQueryParameters> | undefined): Promise<ConversationMemberCollectionResponse | undefined>;
/**
* Add a new conversationMember to a team.
* @param body The request body
* @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
* @returns {Promise<ConversationMember>}
* @throws {ODataError} error when the service returns a 4XX or 5XX status code
* @see {@link https://learn.microsoft.com/graph/api/team-post-members?view=graph-rest-1.0|Find more info here}
*/
post(body: ConversationMember, requestConfiguration?: RequestConfiguration<object> | undefined): Promise<ConversationMember | undefined>;
/**
* Get the conversationMember collection of a team. The membership IDs returned by the server must be treated as opaque strings. The client shouldn't try to parse or make assumptions about these resource IDs. In the future, membership results can include users from various tenants, as indicated in the response. Clients should avoid assuming that all members exclusively belong to the current tenant.
* @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
* @returns {RequestInformation}
*/
toGetRequestInformation(requestConfiguration?: RequestConfiguration<MembersRequestBuilderGetQueryParameters> | undefined): RequestInformation;
/**
* Add a new conversationMember to a team.
* @param body The request body
* @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
* @returns {RequestInformation}
*/
toPostRequestInformation(body: ConversationMember, requestConfiguration?: RequestConfiguration<object> | undefined): RequestInformation;
}
/**
* Get the conversationMember collection of a team. The membership IDs returned by the server must be treated as opaque strings. The client shouldn't try to parse or make assumptions about these resource IDs. In the future, membership results can include users from various tenants, as indicated in the response. Clients should avoid assuming that all members exclusively belong to the current tenant.
*/
export interface MembersRequestBuilderGetQueryParameters {
/**
* Include count of items
*/
count?: boolean;
/**
* Expand related entities
*/
expand?: string[];
/**
* Filter items by property values
*/
filter?: string;
/**
* Order items by property values
*/
orderby?: string[];
/**
* Search items by search phrases
*/
search?: string;
/**
* Select properties to be returned
*/
select?: string[];
/**
* Skip the first n items
*/
skip?: number;
/**
* Show only the first n items
*/
top?: number;
}
/**
* Uri template for the request builder.
*/
export declare const MembersRequestBuilderUriTemplate = "{+baseurl}/teams/{team%2Did}/members{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}";
/**
* Metadata for all the navigation properties in the request builder.
*/
export declare const MembersRequestBuilderNavigationMetadata: Record<Exclude<keyof MembersRequestBuilder, KeysToExcludeForNavigationMetadata>, NavigationMetadata>;
/**
* Metadata for all the requests in the request builder.
*/
export declare const MembersRequestBuilderRequestsMetadata: RequestsMetadata;
//# sourceMappingURL=index.d.ts.map