@types/office-js 1.0.490 → 1.0.492
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.
- office-js/README.md +1 -1
- office-js/index.d.ts +15 -58
- office-js/package.json +2 -2
office-js/README.md
CHANGED
|
@@ -8,7 +8,7 @@ This package contains type definitions for office-js (https://github.com/OfficeD
|
|
|
8
8
|
Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/office-js.
|
|
9
9
|
|
|
10
10
|
### Additional Details
|
|
11
|
-
* Last updated:
|
|
11
|
+
* Last updated: Sat, 19 Apr 2025 18:36:48 GMT
|
|
12
12
|
* Dependencies: none
|
|
13
13
|
|
|
14
14
|
# Credits
|
office-js/index.d.ts
CHANGED
|
@@ -15410,14 +15410,6 @@ declare namespace Office {
|
|
|
15410
15410
|
* <td>New messages and message replies</td>
|
|
15411
15411
|
* </tr>
|
|
15412
15412
|
* <tr>
|
|
15413
|
-
* <td>IPM.Note.SMIME</td>
|
|
15414
|
-
* <td>Encrypted messages that can also be signed</td>
|
|
15415
|
-
* </tr>
|
|
15416
|
-
* <tr>
|
|
15417
|
-
* <td>IPM.Note.SMIME.MultipartSigned</td>
|
|
15418
|
-
* <td>Clear-signed messages</td>
|
|
15419
|
-
* </tr>
|
|
15420
|
-
* <tr>
|
|
15421
15413
|
* <td>IPM.Schedule.Meeting.Request</td>
|
|
15422
15414
|
* <td>Meeting requests</td>
|
|
15423
15415
|
* </tr>
|
|
@@ -15469,14 +15461,6 @@ declare namespace Office {
|
|
|
15469
15461
|
* <td>New messages and message replies</td>
|
|
15470
15462
|
* </tr>
|
|
15471
15463
|
* <tr>
|
|
15472
|
-
* <td>IPM.Note.SMIME</td>
|
|
15473
|
-
* <td>Encrypted messages that can also be signed</td>
|
|
15474
|
-
* </tr>
|
|
15475
|
-
* <tr>
|
|
15476
|
-
* <td>IPM.Note.SMIME.MultipartSigned</td>
|
|
15477
|
-
* <td>Clear-signed messages</td>
|
|
15478
|
-
* </tr>
|
|
15479
|
-
* <tr>
|
|
15480
15464
|
* <td>IPM.Schedule.Meeting.Request</td>
|
|
15481
15465
|
* <td>Meeting requests</td>
|
|
15482
15466
|
* </tr>
|
|
@@ -16025,14 +16009,6 @@ declare namespace Office {
|
|
|
16025
16009
|
* <td>New messages and message replies</td>
|
|
16026
16010
|
* </tr>
|
|
16027
16011
|
* <tr>
|
|
16028
|
-
* <td>IPM.Note.SMIME</td>
|
|
16029
|
-
* <td>Encrypted messages that can also be signed</td>
|
|
16030
|
-
* </tr>
|
|
16031
|
-
* <tr>
|
|
16032
|
-
* <td>IPM.Note.SMIME.MultipartSigned</td>
|
|
16033
|
-
* <td>Clear-signed messages</td>
|
|
16034
|
-
* </tr>
|
|
16035
|
-
* <tr>
|
|
16036
16012
|
* <td>IPM.Schedule.Meeting.Request</td>
|
|
16037
16013
|
* <td>Meeting requests</td>
|
|
16038
16014
|
* </tr>
|
|
@@ -17102,8 +17078,9 @@ declare namespace Office {
|
|
|
17102
17078
|
*
|
|
17103
17079
|
* **Important**:
|
|
17104
17080
|
*
|
|
17105
|
-
* -
|
|
17106
|
-
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens
|
|
17081
|
+
* - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
|
|
17082
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens have been turned off by default for most Exchange Online tenants.
|
|
17083
|
+
* Administrators can reenable legacy tokens for tenants and add-ins until June 2025. In October 2025, legacy tokens will be completely turned off for all tenants.
|
|
17107
17084
|
* This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
|
|
17108
17085
|
* which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
|
|
17109
17086
|
* Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}.
|
|
@@ -17621,8 +17598,9 @@ declare namespace Office {
|
|
|
17621
17598
|
*
|
|
17622
17599
|
* **Important**:
|
|
17623
17600
|
*
|
|
17624
|
-
* -
|
|
17625
|
-
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens
|
|
17601
|
+
* - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
|
|
17602
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens have been turned off by default for most Exchange Online tenants.
|
|
17603
|
+
* Administrators can reenable legacy tokens for tenants and add-ins until June 2025. In October 2025, legacy tokens will be completely turned off for all tenants.
|
|
17626
17604
|
* This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
|
|
17627
17605
|
* which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
|
|
17628
17606
|
* Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}.
|
|
@@ -17725,8 +17703,9 @@ declare namespace Office {
|
|
|
17725
17703
|
*
|
|
17726
17704
|
* **Important**:
|
|
17727
17705
|
*
|
|
17728
|
-
* -
|
|
17729
|
-
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens
|
|
17706
|
+
* - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
|
|
17707
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens have been turned off by default for most Exchange Online tenants.
|
|
17708
|
+
* Administrators can reenable legacy tokens for tenants and add-ins until June 2025. In October 2025, legacy tokens will be completely turned off for all tenants.
|
|
17730
17709
|
* This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
|
|
17731
17710
|
* which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
|
|
17732
17711
|
* Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}.
|
|
@@ -17899,8 +17878,9 @@ declare namespace Office {
|
|
|
17899
17878
|
*
|
|
17900
17879
|
* **Important**:
|
|
17901
17880
|
*
|
|
17902
|
-
* -
|
|
17903
|
-
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens
|
|
17881
|
+
* - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
|
|
17882
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens have been turned off by default for most Exchange Online tenants.
|
|
17883
|
+
* Administrators can reenable legacy tokens for tenants and add-ins until June 2025. In October 2025, legacy tokens will be completely turned off for all tenants.
|
|
17904
17884
|
* This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
|
|
17905
17885
|
* which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
|
|
17906
17886
|
* Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}.
|
|
@@ -18014,8 +17994,9 @@ declare namespace Office {
|
|
|
18014
17994
|
*
|
|
18015
17995
|
* **Important**:
|
|
18016
17996
|
*
|
|
18017
|
-
* -
|
|
18018
|
-
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens
|
|
17997
|
+
* - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
|
|
17998
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens have been turned off by default for most Exchange Online tenants.
|
|
17999
|
+
* Administrators can reenable legacy tokens for tenants and add-ins until June 2025. In October 2025, legacy tokens will be completely turned off for all tenants.
|
|
18019
18000
|
* This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
|
|
18020
18001
|
* which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
|
|
18021
18002
|
* Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}.
|
|
@@ -19324,14 +19305,6 @@ declare namespace Office {
|
|
|
19324
19305
|
* <td>New messages and message replies</td>
|
|
19325
19306
|
* </tr>
|
|
19326
19307
|
* <tr>
|
|
19327
|
-
* <td>IPM.Note.SMIME</td>
|
|
19328
|
-
* <td>Encrypted messages that can also be signed</td>
|
|
19329
|
-
* </tr>
|
|
19330
|
-
* <tr>
|
|
19331
|
-
* <td>IPM.Note.SMIME.MultipartSigned</td>
|
|
19332
|
-
* <td>Clear-signed messages</td>
|
|
19333
|
-
* </tr>
|
|
19334
|
-
* <tr>
|
|
19335
19308
|
* <td>IPM.Schedule.Meeting.Request</td>
|
|
19336
19309
|
* <td>Meeting requests</td>
|
|
19337
19310
|
* </tr>
|
|
@@ -19383,14 +19356,6 @@ declare namespace Office {
|
|
|
19383
19356
|
* <td>New messages and message replies</td>
|
|
19384
19357
|
* </tr>
|
|
19385
19358
|
* <tr>
|
|
19386
|
-
* <td>IPM.Note.SMIME</td>
|
|
19387
|
-
* <td>Encrypted messages that can also be signed</td>
|
|
19388
|
-
* </tr>
|
|
19389
|
-
* <tr>
|
|
19390
|
-
* <td>IPM.Note.SMIME.MultipartSigned</td>
|
|
19391
|
-
* <td>Clear-signed messages</td>
|
|
19392
|
-
* </tr>
|
|
19393
|
-
* <tr>
|
|
19394
19359
|
* <td>IPM.Schedule.Meeting.Request</td>
|
|
19395
19360
|
* <td>Meeting requests</td>
|
|
19396
19361
|
* </tr>
|
|
@@ -20192,14 +20157,6 @@ declare namespace Office {
|
|
|
20192
20157
|
* <td>New messages and message replies</td>
|
|
20193
20158
|
* </tr>
|
|
20194
20159
|
* <tr>
|
|
20195
|
-
* <td>IPM.Note.SMIME</td>
|
|
20196
|
-
* <td>Encrypted messages that can also be signed</td>
|
|
20197
|
-
* </tr>
|
|
20198
|
-
* <tr>
|
|
20199
|
-
* <td>IPM.Note.SMIME.MultipartSigned</td>
|
|
20200
|
-
* <td>Clear-signed messages</td>
|
|
20201
|
-
* </tr>
|
|
20202
|
-
* <tr>
|
|
20203
20160
|
* <td>IPM.Schedule.Meeting.Request</td>
|
|
20204
20161
|
* <td>Meeting requests</td>
|
|
20205
20162
|
* </tr>
|
office-js/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@types/office-js",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.492",
|
|
4
4
|
"description": "TypeScript definitions for office-js",
|
|
5
5
|
"homepage": "https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/office-js",
|
|
6
6
|
"license": "MIT",
|
|
@@ -46,6 +46,6 @@
|
|
|
46
46
|
"scripts": {},
|
|
47
47
|
"dependencies": {},
|
|
48
48
|
"peerDependencies": {},
|
|
49
|
-
"typesPublisherContentHash": "
|
|
49
|
+
"typesPublisherContentHash": "91fe620076b1f4451e70af65544c67f736b85b6a9488c906a9c40091ce149c68",
|
|
50
50
|
"typeScriptVersion": "5.1"
|
|
51
51
|
}
|