@microsoft/msgraph-sdk-groups 1.0.0-preview.29 → 1.0.0-preview.30

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/groups/index.d.ts CHANGED
@@ -45,12 +45,12 @@ export interface GroupsRequestBuilder extends BaseRequestBuilder<GroupsRequestBu
45
45
  */
46
46
  get(requestConfiguration?: RequestConfiguration<GroupsRequestBuilderGetQueryParameters> | undefined): Promise<GroupCollectionResponse | undefined>;
47
47
  /**
48
- * Create a new group object if it doesn't exist, or update the properties of an existing group object.You can create or update the following types of group: By default, this operation returns only a subset of the properties for each group. For a list of properties that are returned by default, see the Properties section of the group resource. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option.
48
+ * Create a new group as specified in the request body. You can create the following types of groups: This operation returns by default only a subset of the properties for each group. These default properties are noted in the Properties section. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option.
49
49
  * @param body The request body
50
50
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
51
51
  * @returns {Promise<Group>}
52
52
  * @throws {ODataError} error when the service returns a 4XX or 5XX status code
53
- * @see {@link https://learn.microsoft.com/graph/api/group-upsert?view=graph-rest-1.0|Find more info here}
53
+ * @see {@link https://learn.microsoft.com/graph/api/group-post-groups?view=graph-rest-1.0|Find more info here}
54
54
  */
55
55
  post(body: Group, requestConfiguration?: RequestConfiguration<object> | undefined): Promise<Group | undefined>;
56
56
  /**
@@ -60,7 +60,7 @@ export interface GroupsRequestBuilder extends BaseRequestBuilder<GroupsRequestBu
60
60
  */
61
61
  toGetRequestInformation(requestConfiguration?: RequestConfiguration<GroupsRequestBuilderGetQueryParameters> | undefined): RequestInformation;
62
62
  /**
63
- * Create a new group object if it doesn't exist, or update the properties of an existing group object.You can create or update the following types of group: By default, this operation returns only a subset of the properties for each group. For a list of properties that are returned by default, see the Properties section of the group resource. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option.
63
+ * Create a new group as specified in the request body. You can create the following types of groups: This operation returns by default only a subset of the properties for each group. These default properties are noted in the Properties section. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option.
64
64
  * @param body The request body
65
65
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
66
66
  * @returns {RequestInformation}
@@ -25,12 +25,12 @@ export interface ConversationsRequestBuilder extends BaseRequestBuilder<Conversa
25
25
  */
26
26
  get(requestConfiguration?: RequestConfiguration<ConversationsRequestBuilderGetQueryParameters> | undefined): Promise<ConversationCollectionResponse | undefined>;
27
27
  /**
28
- * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions.
28
+ * Use reply thread or reply post to further post to that conversation.
29
29
  * @param body The request body
30
30
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
31
31
  * @returns {Promise<Conversation>}
32
32
  * @throws {ODataError} error when the service returns a 4XX or 5XX status code
33
- * @see {@link https://learn.microsoft.com/graph/api/opentypeextension-post-opentypeextension?view=graph-rest-1.0|Find more info here}
33
+ * @see {@link https://learn.microsoft.com/graph/api/group-post-conversations?view=graph-rest-1.0|Find more info here}
34
34
  */
35
35
  post(body: Conversation, requestConfiguration?: RequestConfiguration<object> | undefined): Promise<Conversation | undefined>;
36
36
  /**
@@ -40,7 +40,7 @@ export interface ConversationsRequestBuilder extends BaseRequestBuilder<Conversa
40
40
  */
41
41
  toGetRequestInformation(requestConfiguration?: RequestConfiguration<ConversationsRequestBuilderGetQueryParameters> | undefined): RequestInformation;
42
42
  /**
43
- * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions.
43
+ * Use reply thread or reply post to further post to that conversation.
44
44
  * @param body The request body
45
45
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
46
46
  * @returns {RequestInformation}
@@ -13,7 +13,7 @@ export interface ConversationItemRequestBuilder extends BaseRequestBuilder<Conve
13
13
  * Delete conversation.
14
14
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
15
15
  * @throws {ODataError} error when the service returns a 4XX or 5XX status code
16
- * @see {@link https://learn.microsoft.com/graph/api/conversation-delete?view=graph-rest-1.0|Find more info here}
16
+ * @see {@link https://learn.microsoft.com/graph/api/group-delete-conversation?view=graph-rest-1.0|Find more info here}
17
17
  */
18
18
  delete(requestConfiguration?: RequestConfiguration<object> | undefined): Promise<void>;
19
19
  /**
@@ -30,15 +30,15 @@ export interface ReplyPostRequestBody extends AdditionalDataHolder, BackedModel,
30
30
  */
31
31
  export interface ReplyRequestBuilder extends BaseRequestBuilder<ReplyRequestBuilder> {
32
32
  /**
33
- * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions.
33
+ * Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation.
34
34
  * @param body The request body
35
35
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
36
36
  * @throws {ODataError} error when the service returns a 4XX or 5XX status code
37
- * @see {@link https://learn.microsoft.com/graph/api/opentypeextension-post-opentypeextension?view=graph-rest-1.0|Find more info here}
37
+ * @see {@link https://learn.microsoft.com/graph/api/post-reply?view=graph-rest-1.0|Find more info here}
38
38
  */
39
39
  post(body: ReplyPostRequestBody, requestConfiguration?: RequestConfiguration<object> | undefined): Promise<void>;
40
40
  /**
41
- * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions.
41
+ * Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation.
42
42
  * @param body The request body
43
43
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
44
44
  * @returns {RequestInformation}
@@ -17,7 +17,7 @@ export interface DeltaGetResponse extends BaseDeltaFunctionResponse, Parsable {
17
17
  */
18
18
  export interface DeltaRequestBuilder extends BaseRequestBuilder<DeltaRequestBuilder> {
19
19
  /**
20
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
20
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
21
21
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
22
22
  * @returns {Promise<DeltaGetResponse>}
23
23
  * @throws {ODataError} error when the service returns a 4XX or 5XX status code
@@ -25,14 +25,14 @@ export interface DeltaRequestBuilder extends BaseRequestBuilder<DeltaRequestBuil
25
25
  */
26
26
  get(requestConfiguration?: RequestConfiguration<DeltaRequestBuilderGetQueryParameters> | undefined): Promise<DeltaGetResponse | undefined>;
27
27
  /**
28
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
28
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
29
29
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
30
30
  * @returns {RequestInformation}
31
31
  */
32
32
  toGetRequestInformation(requestConfiguration?: RequestConfiguration<DeltaRequestBuilderGetQueryParameters> | undefined): RequestInformation;
33
33
  }
34
34
  /**
35
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
35
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
36
36
  */
37
37
  export interface DeltaRequestBuilderGetQueryParameters {
38
38
  /**
@@ -17,7 +17,7 @@ export interface DeltaGetResponse extends BaseDeltaFunctionResponse, Parsable {
17
17
  */
18
18
  export interface DeltaRequestBuilder extends BaseRequestBuilder<DeltaRequestBuilder> {
19
19
  /**
20
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
20
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
21
21
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
22
22
  * @returns {Promise<DeltaGetResponse>}
23
23
  * @throws {ODataError} error when the service returns a 4XX or 5XX status code
@@ -25,14 +25,14 @@ export interface DeltaRequestBuilder extends BaseRequestBuilder<DeltaRequestBuil
25
25
  */
26
26
  get(requestConfiguration?: RequestConfiguration<DeltaRequestBuilderGetQueryParameters> | undefined): Promise<DeltaGetResponse | undefined>;
27
27
  /**
28
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
28
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
29
29
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
30
30
  * @returns {RequestInformation}
31
31
  */
32
32
  toGetRequestInformation(requestConfiguration?: RequestConfiguration<DeltaRequestBuilderGetQueryParameters> | undefined): RequestInformation;
33
33
  }
34
34
  /**
35
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
35
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
36
36
  */
37
37
  export interface DeltaRequestBuilderGetQueryParameters {
38
38
  /**
@@ -17,7 +17,7 @@ export interface DeltaGetResponse extends BaseDeltaFunctionResponse, Parsable {
17
17
  */
18
18
  export interface DeltaRequestBuilder extends BaseRequestBuilder<DeltaRequestBuilder> {
19
19
  /**
20
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
20
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
21
21
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
22
22
  * @returns {Promise<DeltaGetResponse>}
23
23
  * @throws {ODataError} error when the service returns a 4XX or 5XX status code
@@ -25,14 +25,14 @@ export interface DeltaRequestBuilder extends BaseRequestBuilder<DeltaRequestBuil
25
25
  */
26
26
  get(requestConfiguration?: RequestConfiguration<DeltaRequestBuilderGetQueryParameters> | undefined): Promise<DeltaGetResponse | undefined>;
27
27
  /**
28
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
28
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
29
29
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
30
30
  * @returns {RequestInformation}
31
31
  */
32
32
  toGetRequestInformation(requestConfiguration?: RequestConfiguration<DeltaRequestBuilderGetQueryParameters> | undefined): RequestInformation;
33
33
  }
34
34
  /**
35
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
35
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
36
36
  */
37
37
  export interface DeltaRequestBuilderGetQueryParameters {
38
38
  /**
@@ -17,7 +17,7 @@ export interface DeltaGetResponse extends BaseDeltaFunctionResponse, Parsable {
17
17
  */
18
18
  export interface DeltaRequestBuilder extends BaseRequestBuilder<DeltaRequestBuilder> {
19
19
  /**
20
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
20
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
21
21
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
22
22
  * @returns {Promise<DeltaGetResponse>}
23
23
  * @throws {ODataError} error when the service returns a 4XX or 5XX status code
@@ -25,14 +25,14 @@ export interface DeltaRequestBuilder extends BaseRequestBuilder<DeltaRequestBuil
25
25
  */
26
26
  get(requestConfiguration?: RequestConfiguration<DeltaRequestBuilderGetQueryParameters> | undefined): Promise<DeltaGetResponse | undefined>;
27
27
  /**
28
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
28
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
29
29
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
30
30
  * @returns {RequestInformation}
31
31
  */
32
32
  toGetRequestInformation(requestConfiguration?: RequestConfiguration<DeltaRequestBuilderGetQueryParameters> | undefined): RequestInformation;
33
33
  }
34
34
  /**
35
- * Retrieve the list of messages (without the replies) in a channel of a team. By using delta query, you can get new or updated messages in a channel. Delta query supports both full synchronization that retrieves all the messages in the specified channel, and incremental synchronization that retrieves those messages that have been added or changed in the channel since the last synchronization. Typically, you would do an initial full synchronization, and then get incremental changes to that messages view periodically. To get the replies for a message, use the list message replies or the get message reply operation. A GET request with the delta function returns either: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call for that same calendar view. A @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after acquiring @odata.deltaLink). For more information, see the delta query documentation.
35
+ * Get the list of messages from all chats in which a user is a participant, including one-on-one chats, group chats, and meeting chats. When you use delta query, you can get new or updated messages. To get the replies for a message, use the list message replies or the get message reply operations. A GET request with the delta function returns one of the following: State tokens are opaque to the client. To proceed with a round of change tracking, copy and apply the @odata.nextLink or @odata.deltaLink URL returned from the last GET request to the next delta function call. An @odata.deltaLink returned in a response signifies that the current round of change tracking is complete. You can save and use the @odata.deltaLink URL when you begin to retrieve more changes (messages changed or posted after you acquire @odata.deltaLink). For more information, see the delta query documentation.
36
36
  */
37
37
  export interface DeltaRequestBuilderGetQueryParameters {
38
38
  /**
@@ -22,11 +22,11 @@ export interface ConversationThreadItemRequestBuilder extends BaseRequestBuilder
22
22
  */
23
23
  delete(requestConfiguration?: RequestConfiguration<object> | undefined): Promise<void>;
24
24
  /**
25
- * Get a specific thread that belongs to a group. You can specify both the parent conversation and the thread, or, you can specify the thread without referencing the parent conversation.
25
+ * Get a thread object.
26
26
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
27
27
  * @returns {Promise<ConversationThread>}
28
28
  * @throws {ODataError} error when the service returns a 4XX or 5XX status code
29
- * @see {@link https://learn.microsoft.com/graph/api/conversationthread-get?view=graph-rest-1.0|Find more info here}
29
+ * @see {@link https://learn.microsoft.com/graph/api/group-get-thread?view=graph-rest-1.0|Find more info here}
30
30
  */
31
31
  get(requestConfiguration?: RequestConfiguration<ConversationThreadItemRequestBuilderGetQueryParameters> | undefined): Promise<ConversationThread | undefined>;
32
32
  /**
@@ -45,7 +45,7 @@ export interface ConversationThreadItemRequestBuilder extends BaseRequestBuilder
45
45
  */
46
46
  toDeleteRequestInformation(requestConfiguration?: RequestConfiguration<object> | undefined): RequestInformation;
47
47
  /**
48
- * Get a specific thread that belongs to a group. You can specify both the parent conversation and the thread, or, you can specify the thread without referencing the parent conversation.
48
+ * Get a thread object.
49
49
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
50
50
  * @returns {RequestInformation}
51
51
  */
@@ -59,7 +59,7 @@ export interface ConversationThreadItemRequestBuilder extends BaseRequestBuilder
59
59
  toPatchRequestInformation(body: ConversationThread, requestConfiguration?: RequestConfiguration<object> | undefined): RequestInformation;
60
60
  }
61
61
  /**
62
- * Get a specific thread that belongs to a group. You can specify both the parent conversation and the thread, or, you can specify the thread without referencing the parent conversation.
62
+ * Get a thread object.
63
63
  */
64
64
  export interface ConversationThreadItemRequestBuilderGetQueryParameters {
65
65
  /**
@@ -30,15 +30,15 @@ export interface ReplyPostRequestBody extends AdditionalDataHolder, BackedModel,
30
30
  */
31
31
  export interface ReplyRequestBuilder extends BaseRequestBuilder<ReplyRequestBuilder> {
32
32
  /**
33
- * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions.
33
+ * Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation.
34
34
  * @param body The request body
35
35
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
36
36
  * @throws {ODataError} error when the service returns a 4XX or 5XX status code
37
- * @see {@link https://learn.microsoft.com/graph/api/opentypeextension-post-opentypeextension?view=graph-rest-1.0|Find more info here}
37
+ * @see {@link https://learn.microsoft.com/graph/api/post-reply?view=graph-rest-1.0|Find more info here}
38
38
  */
39
39
  post(body: ReplyPostRequestBody, requestConfiguration?: RequestConfiguration<object> | undefined): Promise<void>;
40
40
  /**
41
- * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions.
41
+ * Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation.
42
42
  * @param body The request body
43
43
  * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
44
44
  * @returns {RequestInformation}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@microsoft/msgraph-sdk-groups",
3
- "version": "1.0.0-preview.29",
3
+ "version": "1.0.0-preview.30",
4
4
  "description": "Groups fluent API for Microsoft Graph",
5
5
  "keywords": [
6
6
  "Microsoft",
@@ -35,7 +35,7 @@
35
35
  "@microsoft/kiota-serialization-json": "^1.0.0-preview.39",
36
36
  "@microsoft/kiota-serialization-multipart": "^1.0.0-preview.18",
37
37
  "@microsoft/kiota-serialization-text": "^1.0.0-preview.36",
38
- "@microsoft/msgraph-sdk": "^1.0.0-preview.29",
38
+ "@microsoft/msgraph-sdk": "^1.0.0-preview.30",
39
39
  "guid-typescript": "^1.0.9",
40
40
  "tslib": "^2.6.2"
41
41
  },
@@ -43,5 +43,5 @@
43
43
  "typescript": "^5.3.3"
44
44
  },
45
45
  "type": "module",
46
- "gitHead": "3588db2b255734a43036a0a0e79434a31c821f3b"
46
+ "gitHead": "722436d5c5202b7dd10f048c1cdf6946cd67fff6"
47
47
  }