@elliemae/pui-scripting-object 1.40.4 → 1.41.1

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.
@@ -56,7 +56,7 @@ export type LaunchCategoryOptions = {
56
56
  */
57
57
  targetType: NavigationType;
58
58
  /**
59
- * additional query parameters to be passed to the redirect location. For example, if rediret requested to services area with targetParams { "key1": "value1", "key2": "value2"}, the url will have querystring as services?query={"transactionId":123, "orderId":456, "key1": "value1", "key2": "value2"}
59
+ * additional query parameters to be passed to the redirect location. For example, if rediret requested to services area with targetParams \\{ 'key1': 'value1', 'key2': 'value2'\\}, the url will have querystring as services?query=\\{'transactionId':123, 'orderId':456, 'key1': 'value1', 'key2': 'value2'\\}
60
60
  */
61
61
  targetParams?: Record<string, string>;
62
62
  };
@@ -106,7 +106,7 @@ export type LaunchServiceSetupOptions = {
106
106
  */
107
107
  targetType: NavigationType;
108
108
  /**
109
- * additional query parameters to be passed to the redirect location. For example, if rediret requested to services area with targetParams { "key1": "value1", "key2": "value2"}, the url will have querystring as services?query={"transactionId":123, "orderId":456, "key1": "value1", "key2": "value2"}
109
+ * additional query parameters to be passed to the redirect location. For example, if rediret requested to services area with targetParams \\{ 'key1': 'value1', 'key2': 'value2'\\}, the url will have querystring as services?query=\\{'transactionId':123, 'orderId':456, 'key1': 'value1', 'key2': 'value2'\\}
110
110
  */
111
111
  targetParams?: Record<string, string>;
112
112
  };
@@ -152,7 +152,7 @@ export type LaunchProviderOptions = {
152
152
  */
153
153
  targetType: NavigationType;
154
154
  /**
155
- * additional query parameters to be passed to the redirect location. For example, if rediret requested to services area with targetParams { "key1": "value1", "key2": "value2"}, the url will have querystring as services?query={"transactionId":123, "orderId":456, "key1": "value1", "key2": "value2"}
155
+ * additional query parameters to be passed to the redirect location. For example, if rediret requested to services area with targetParams \\{ 'key1': 'value1', 'key2': 'value2'\\}, the url will have querystring as services?query=\\{'transactionId':123, 'orderId':456, 'key1': 'value1', 'key2': 'value2'\\}
156
156
  */
157
157
  targetParams?: Record<string, string>;
158
158
  };
@@ -178,10 +178,6 @@ export type LaunchProviderOptions = {
178
178
  * Enables applications to place service orders, independent of SLP (Service Landing Page) application
179
179
  * Errors thrown by the service order integration will be returned to the caller of this Scripting Object method
180
180
  *
181
- * #### Product Compatibility:
182
- * | | Encompass | Encompass Web | TPO | Consumer Connect |
183
- * :-----:|:-----: |:-----: |:-----: |:-----: |
184
- * | all | ✖️ | ✔ | ✖️ | ✖️ |
185
181
  */
186
182
  export interface IService extends IScriptingObject {
187
183
  /**
@@ -189,11 +185,6 @@ export interface IService extends IScriptingObject {
189
185
  * @param {ServiceSetupCategory} category - service setup category
190
186
  * @param providerId - unique id of the service setup provider
191
187
  * @returns {Array<ServiceSetup>} list of service setups matching the input criteria. Empty list if no service setups are found
192
- *
193
- * #### Product Compatibility:
194
- * | | Encompass | Encompass Web | TPO | Consumer Connect |
195
- * :-----:|:-----: |:-----: |:-----: |:-----: |
196
- * | all | ✖️ | ✔ | ✖️ | ✖️ |
197
188
  */
198
189
  getEligibleServices: (category: ServiceSetupCategory, providerId?: string) => Promise<Array<ServiceSetup>>;
199
190
  /**
@@ -205,61 +196,46 @@ export interface IService extends IScriptingObject {
205
196
  *
206
197
  * After the integration flow is complete, user will be redirected to the location provided in the input parameter.
207
198
  *
208
- * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?query={"transactionId":123, "orderId":456}
199
+ * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?query=\\{'transactionId':123, 'orderId':456\\}
209
200
  *
210
201
  * Supports EPC & EVP service order integrations
211
202
  * @param category - name of the service category
212
203
  * @param {LaunchCategoryOptions} options - options for launching the service order integration
213
204
  * @returns None
214
- *
215
- * #### Product Compatibility:
216
- * | | Encompass | Encompass Web | TPO | Consumer Connect |
217
- * :-----:|:-----: |:-----: |:-----: |:-----: |
218
- * | all | ✖️ | ✔ | ✖️ | ✖️ |
219
205
  */
220
206
  launchByCategory: (category: string, options: LaunchCategoryOptions) => Promise<void>;
221
207
  /**
222
- * Launch a service intergration for a specific service setup to place a new service order or view existing order.
208
+ * Launch a service intergration for a specific provider to place a new service order or view existing order
223
209
  *
224
210
  * Commit all unsaved loan changes using loan.commit, before calling this method.
225
211
  *
226
- * This method will unload the current microapp and navigate to the service order integration.
212
+ * This method will unload the current microapp and navigate to the service order integration
227
213
  *
228
214
  * After the integration flow is complete, user will be redirected to the location provided in the input parameter.
229
215
  *
230
- * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?query={"transactionId":123, "orderId":456}
216
+ * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?query=\\{'transactionId':123, 'orderId':456\\}
231
217
  *
232
218
  * Supports EPC & EVP service order integrations
233
- * @param serviceSetupId - unique id of the service setup
234
- * @param {LaunchServiceSetupOptions} options - options for launching the service order integration
219
+ * @param providerId - unique id of the service provider
220
+ * @param {LaunchProviderOptions} options - options for launching the service order integration
235
221
  * @returns None
236
- *
237
- * #### Product Compatibility:
238
- * | | Encompass | Encompass Web | TPO | Consumer Connect |
239
- * :-----:|:-----: |:-----: |:-----: |:-----: |
240
- * | all | ✖️ | ✔ | ✖️ | ✖️ |
241
222
  */
242
- launchByServiceSetup: (serviceSetupId: string, options: LaunchServiceSetupOptions) => Promise<void>;
223
+ launchByProvider: (providerId: string, options: LaunchProviderOptions) => Promise<void>;
243
224
  /**
244
- * Launch a service intergration for a specific provider to place a new service order or view existing order
225
+ * Launch a service intergration for a specific service setup to place a new service order or view existing order.
245
226
  *
246
227
  * Commit all unsaved loan changes using loan.commit, before calling this method.
247
228
  *
248
- * This method will unload the current microapp and navigate to the service order integration
229
+ * This method will unload the current microapp and navigate to the service order integration.
249
230
  *
250
231
  * After the integration flow is complete, user will be redirected to the location provided in the input parameter.
251
232
  *
252
- * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?query={"transactionId":123, "orderId":456}
233
+ * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?query=\\{'transactionId':123, 'orderId':456\\}
253
234
  *
254
235
  * Supports EPC & EVP service order integrations
255
- * @param providerId - unique id of the service provider
256
- * @param {LaunchProviderOptions} options - options for launching the service order integration
236
+ * @param serviceSetupId - unique id of the service setup
237
+ * @param {LaunchServiceSetupOptions} options - options for launching the service order integration
257
238
  * @returns None
258
- *
259
- * #### Product Compatibility:
260
- * | | Encompass | Encompass Web | TPO | Consumer Connect |
261
- * :-----:|:-----: |:-----: |:-----: |:-----: |
262
- * | all | ✖️ | ✖️ | ✖️ | ✖️ |
263
239
  */
264
- launchByProvider: (providerId: string, options: LaunchProviderOptions) => Promise<void>;
240
+ launchByServiceSetup: (serviceSetupId: string, options: LaunchServiceSetupOptions) => Promise<void>;
265
241
  }
@@ -3,15 +3,16 @@ import { IScriptingObject } from '../scriptingObject.js';
3
3
  * store and retrieves values in host application's session storage
4
4
  */
5
5
  export interface ISession extends IScriptingObject {
6
+ /**
7
+ * get a value from the session storage
8
+ * @param key unique key to retrieve the value
9
+ * @returns value stored in the session storage
10
+ */
11
+ get(key: string): Promise<string>;
6
12
  /**
7
13
  * set a value in the session storage
8
14
  * @param key unique key to store the value
9
15
  * @param value value to be stored
10
16
  */
11
17
  set(key: string, value: string): Promise<void>;
12
- /**
13
- * get a value from the session storage
14
- * @param key unique key to retrieve the value
15
- */
16
- get(key: string): Promise<string>;
17
18
  }
@@ -19,20 +19,30 @@ export type TransactionInfo = {
19
19
  */
20
20
  export interface ITransaction extends IScriptingObject {
21
21
  /**
22
- * Provide the necessary information for your application's user-interface to:
23
- * Access transaction origination information and bootstrap its user interaction
24
- * Know if it was launched in the context of an existing transaction, so it can present the relevant view
25
- * @returns transaction origination information
22
+ * Navigate your users back to where they left off in the host Encompass application,
23
+ * after they have canceled an interaction with your application's user-interface without having
24
+ * initiated a transaction request (or any other related task) that they were working on.
25
+ * This signals a cancelation outcome to the host Encompass application -
26
+ * how this is handled by the host upon user navigation can vary across applications
26
27
  */
27
- getOrigin(): Promise<OriginDetails>;
28
+ cancel(): Promise<void>;
28
29
  /**
29
- * Refresh your application's transaction origination context - if your current one expires.
30
- * This method returns a new originId and partnerAccessToken - which your application back-end can use to retrieve a refreshed transaction origin:
31
- * A fresh snapshot of the loan data your application is entitled to receive in a transaction origin
32
- * A a fresh snapshot of the user's credential set configured by their Administrator for use with your application
33
- * @returns transaction origination information
30
+ * Navigate your users back to where they left off in the host Encompass application,
31
+ * after they are done interacting with your application's user-interface
34
32
  */
35
- refreshOrigin(): Promise<OriginDetails>;
33
+ close(): Promise<void>;
34
+ /**
35
+ * initiate a new transaction with your integration
36
+ * @param options details of the transaction to be initiated
37
+ * @returns transaction id
38
+ */
39
+ create(options: TransactionDetails): Promise<TransactionInfo>;
40
+ /**
41
+ * Allow Lenders to initiate an event/message for the subject transaction with your integration
42
+ * @param options details of the event/message to be initiated
43
+ * @returns transaction event id
44
+ */
45
+ createEvent(options: TransactionEvent): Promise<TransactionInfo>;
36
46
  /**
37
47
  * Allow Lenders to use your integration to upload files from their
38
48
  * local drive as an attachment to a new transaction.
@@ -43,11 +53,52 @@ export interface ITransaction extends IScriptingObject {
43
53
  */
44
54
  createResource(options: ResourceOptions): Promise<ResourceDetails>;
45
55
  /**
46
- * initiate a new transaction with your integration
47
- * @param options details of the transaction to be initiated
48
- * @returns transaction id
56
+ * Navigate your users back to where they left off in the host Encompass application,
57
+ * after their has been an error (application error or workflow error) on your integrations user-interface.
58
+ * This signals an error outcome to the host Encompass application -
59
+ * how this is handled by the host upon user navigation can vary across applications
49
60
  */
50
- create(options: TransactionDetails): Promise<TransactionInfo>;
61
+ error(): Promise<void>;
62
+ /**
63
+ * Retrieve the transaction in whose context your integration is operating in, utilized by methods that operate on an existing transaction.
64
+ * The methods that currently fall into this category are:
65
+ * transaction.update
66
+ * transaction.createEvent
67
+ * Although integrations are free to set the transactional context they are operating in
68
+ * (using the transaction.set method) , which may be necessary when providing views that
69
+ * allow users to switch between and perform actions on multiple transactions,
70
+ * the host application implicitly alters the transactional context in certain scenarios:
71
+ *
72
+ * Implicit transaction context setting!
73
+ * If your integration is launched by a user in the context of an existing transaction,
74
+ * such as from the services page on Loan Officer Connect, the document icon on the services
75
+ * side-nav in Encompass Desktop or on a loan application in Consumer Connect is set to said transaction.
76
+ * Every time a new transaction is created during a user's interaction with your integration,
77
+ * the context is set to the last created transaction.
78
+ * If the integration was initially launched in the context of an existing transaction,
79
+ * the transaction.getOrigin method will always return the original transactionId the integration was launched
80
+ * in the context of, no matter how many times the transaction is set in the current interaction.
81
+ * You can leverage this to track the initial transaction context for a user interaction
82
+ *
83
+ * The current transactional context your integration operates in can be queried using the transaction.get method
84
+ * @returns transaction id details
85
+ */
86
+ get(): Promise<TransactionInfo>;
87
+ /**
88
+ * Provide the necessary information for your application's user-interface to:
89
+ * Access transaction origination information and bootstrap its user interaction
90
+ * Know if it was launched in the context of an existing transaction, so it can present the relevant view
91
+ * @returns transaction origination information
92
+ */
93
+ getOrigin(): Promise<OriginDetails>;
94
+ /**
95
+ * Refresh your application's transaction origination context - if your current one expires.
96
+ * This method returns a new originId and partnerAccessToken - which your application back-end can use to retrieve a refreshed transaction origin:
97
+ * A fresh snapshot of the loan data your application is entitled to receive in a transaction origin
98
+ * A a fresh snapshot of the user's credential set configured by their Administrator for use with your application
99
+ * @returns transaction origination information
100
+ */
101
+ refreshOrigin(): Promise<OriginDetails>;
51
102
  /**
52
103
  * Set the transaction in whose context you want to invoke methods that operate on an existing transaction.
53
104
  * The subject transaction must be one that was created for the current loan and EPC product.
@@ -77,31 +128,6 @@ export interface ITransaction extends IScriptingObject {
77
128
  * @returns transaction that has been set
78
129
  */
79
130
  set(options: TransactionInfo): Promise<TransactionInfo>;
80
- /**
81
- * Retrieve the transaction in whose context your integration is operating in, utilized by methods that operate on an existing transaction.
82
- * The methods that currently fall into this category are:
83
- * transaction.update
84
- * transaction.createEvent
85
- * Although integrations are free to set the transactional context they are operating in
86
- * (using the transaction.set method) , which may be necessary when providing views that
87
- * allow users to switch between and perform actions on multiple transactions,
88
- * the host application implicitly alters the transactional context in certain scenarios:
89
- *
90
- * Implicit transaction context setting!
91
- * If your integration is launched by a user in the context of an existing transaction,
92
- * such as from the services page on Loan Officer Connect, the document icon on the services
93
- * side-nav in Encompass Desktop or on a loan application in Consumer Connect is set to said transaction.
94
- * Every time a new transaction is created during a user's interaction with your integration,
95
- * the context is set to the last created transaction.
96
- * If the integration was initially launched in the context of an existing transaction,
97
- * the transaction.getOrigin method will always return the original transactionId the integration was launched
98
- * in the context of, no matter how many times the transaction is set in the current interaction.
99
- * You can leverage this to track the initial transaction context for a user interaction
100
- *
101
- * The current transactional context your integration operates in can be queried using the transaction.get method
102
- * @returns transaction id details
103
- */
104
- get(): Promise<TransactionInfo>;
105
131
  /**
106
132
  * Allow Lenders to update an existing transaction by attaching new resources or updating
107
133
  * the request options associated with the transaction.
@@ -122,30 +148,4 @@ export interface ITransaction extends IScriptingObject {
122
148
  * @returns transaction id
123
149
  */
124
150
  update(options: TransactionDetails): Promise<TransactionInfo>;
125
- /**
126
- * Allow Lenders to initiate an event/message for the subject transaction with your integration
127
- * @param options details of the event/message to be initiated
128
- * @returns transaction event id
129
- */
130
- createEvent(options: TransactionEvent): Promise<TransactionInfo>;
131
- /**
132
- * Navigate your users back to where they left off in the host Encompass application,
133
- * after they are done interacting with your application's user-interface
134
- */
135
- close(): Promise<void>;
136
- /**
137
- * Navigate your users back to where they left off in the host Encompass application,
138
- * after they have canceled an interaction with your application's user-interface without having
139
- * initiated a transaction request (or any other related task) that they were working on.
140
- * This signals a cancelation outcome to the host Encompass application -
141
- * how this is handled by the host upon user navigation can vary across applications
142
- */
143
- cancel(): Promise<void>;
144
- /**
145
- * Navigate your users back to where they left off in the host Encompass application,
146
- * after their has been an error (application error or workflow error) on your integrations user-interface.
147
- * This signals an error outcome to the host Encompass application -
148
- * how this is handled by the host upon user navigation can vary across applications
149
- */
150
- error(): Promise<void>;
151
151
  }
@@ -45,6 +45,12 @@ export type TransactionTemplateDetails = {
45
45
  * which they can associate with a 1-click/automated ordering business condition set.
46
46
  */
47
47
  export interface ITransactionTemplate extends IScriptingObject {
48
+ /**
49
+ * Navigate the administrator users back to where they left off in the
50
+ * Loan Officer Connect services management application, after they are done interacting
51
+ * with your application's administrator-facing user-interface
52
+ */
53
+ close(): Promise<void>;
48
54
  /**
49
55
  * Discover if your administrator-facing view has been rendered in the context of an existing
50
56
  * transaction request template (in edit mode) or a new transaction request template (in create mode).
@@ -66,10 +72,4 @@ export interface ITransactionTemplate extends IScriptingObject {
66
72
  * @returns success
67
73
  */
68
74
  save(options: TransactionTemplateDetails): Promise<string>;
69
- /**
70
- * Navigate the administrator users back to where they left off in the
71
- * Loan Officer Connect services management application, after they are done interacting
72
- * with your application's administrator-facing user-interface
73
- */
74
- close(): Promise<void>;
75
75
  }
@@ -26,6 +26,13 @@ export declare enum CompleteReason {
26
26
  * create events/messages for a transaction, and more.
27
27
  */
28
28
  export interface ITransactionV2 extends IScriptingObject {
29
+ /**
30
+ * notify host on completion of user interaction with the transaction
31
+ * so that host can perform any necessary post user interaction processing / cleanup.
32
+ * @param id - unique identifier for the transaction
33
+ * @param reason reason for completing the transaction user interaction
34
+ */
35
+ completeUserInteraction(id: string, reason: CompleteReason): Promise<void>;
29
36
  /**
30
37
  * create new transaction
31
38
  * @param options details of the transaction to be created
@@ -41,6 +48,13 @@ export interface ITransactionV2 extends IScriptingObject {
41
48
  * @throws error when event creation fails, TransactionNotFound error for invalid transaction id
42
49
  */
43
50
  createEvent(id: string, options: TransactionEvent): Promise<string>;
51
+ /**
52
+ * Creates new origin and context.
53
+ * @param withLoanData - include loan data in the origin cache
54
+ * @returns service setup origination information
55
+ * @throws OriginNotFound error when origin is not found
56
+ */
57
+ createOrigin(withLoanData: boolean): Promise<OriginDetails>;
44
58
  /**
45
59
  * get necessary details to upload document for specific transaction
46
60
  * @param id - unique identifier for the transaction
@@ -56,13 +70,6 @@ export interface ITransactionV2 extends IScriptingObject {
56
70
  * @throws TransactionNotFound error for invalid transaction id
57
71
  */
58
72
  get(id: string): Promise<TransactionDetails>;
59
- /**
60
- * Creates new origin and context.
61
- * @param withLoanData - include loan data in the origin cache
62
- * @returns service setup origination information
63
- * @throws OriginNotFound error when origin is not found
64
- */
65
- createOrigin(withLoanData: boolean): Promise<OriginDetails>;
66
73
  /**
67
74
  * update existing transaction.
68
75
  * @param id - unique identifier for the transaction
@@ -70,11 +77,4 @@ export interface ITransactionV2 extends IScriptingObject {
70
77
  * @throws error when transaction update fails, TransactionNotFound error for invalid transaction id
71
78
  */
72
79
  update(id: string, options: TransactionDetails): Promise<void>;
73
- /**
74
- * notify host on completion of user interaction with the transaction
75
- * so that host can perform any necessary post user interaction processing / cleanup.
76
- * @param id - unique identifier for the transaction
77
- * @param reason reason for completing the transaction user interaction
78
- */
79
- completeUserInteraction(id: string, reason: CompleteReason): Promise<void>;
80
80
  }
@@ -1,5 +1,5 @@
1
1
  import { BreakPoint } from '@elliemae/pui-theme';
2
- import { IEvent, Listener } from '../event.js';
2
+ import { IEvent } from '../event.js';
3
3
  import { IScriptingObject } from '../scriptingObject.js';
4
4
  /**
5
5
  * window viewport size
@@ -8,6 +8,9 @@ export type ViewportSize = {
8
8
  width: number;
9
9
  height: number;
10
10
  };
11
+ /**
12
+ * window viewport size information
13
+ */
11
14
  type ViewportSizeInfo = {
12
15
  /**
13
16
  * details about the resize event
@@ -16,9 +19,22 @@ type ViewportSizeInfo = {
16
19
  };
17
20
  /**
18
21
  * parent window resize event handler
22
+ * @param params event parameters
23
+ * @param params.obj view object reference
24
+ * @param params.eventName event name
25
+ * @param params.eventParams view port info
26
+ * @param params.eventOptions additional options related to the event
27
+ */
28
+ export type ViewResizeListener = (params: {
29
+ obj: IView;
30
+ eventName: string;
31
+ eventParams: ViewportSizeInfo;
32
+ eventOptions?: Record<string, unknown>;
33
+ }) => void;
34
+ /**
35
+ * window breakpoint information
19
36
  */
20
- export type ViewResizeListener = Listener<IView, ViewportSizeInfo, Record<string, unknown>, void>;
21
- type BreakpointInfo = {
37
+ export type BreakpointInfo = {
22
38
  /**
23
39
  * current breakpoint of the parent window
24
40
  */
@@ -26,36 +42,61 @@ type BreakpointInfo = {
26
42
  };
27
43
  /**
28
44
  * parent window breakpoint change event handler
45
+ * @param params event parameters
46
+ * @param params.obj view object reference
47
+ * @param params.eventName event name
48
+ * @param params.eventParams window breakpoint info
49
+ * @param params.eventOptions additional options related to the event
50
+ */
51
+ export type BreakpointChangeListener = (params: {
52
+ obj: IView;
53
+ eventName: string;
54
+ eventParams: BreakpointInfo;
55
+ eventOptions?: Record<string, unknown>;
56
+ }) => void;
57
+ /**
58
+ * events related to the window
29
59
  */
30
- export type BreakpointChangeListener = Listener<IView, BreakpointInfo, Record<string, unknown>, void>;
31
60
  export type ViewEvents = {
32
- /**
33
- * eent is fired when the parent window is resized
34
- */
35
- 'view.resize': ViewResizeListener;
36
61
  /**
37
62
  * event is fired when the parent window's breakpoint changes
63
+ *
64
+ * Use {@link BreakpointChangeListener} to handle this event
38
65
  */
39
66
  'view.breakpointChange': BreakpointChangeListener;
67
+ /**
68
+ * eent is fired when the parent window is resized
69
+ *
70
+ * Use {@link ViewResizeListener} to handle this event
71
+ */
72
+ 'view.resize': ViewResizeListener;
40
73
  };
41
74
  /**
42
- * Methods view, modify parent's window attributes
75
+ * APIs to interact with the window / viewport
76
+ *
77
+ * See {@link ViewEvents} for supported events
43
78
  */
44
79
  export interface IView extends IScriptingObject {
45
- /**
46
- * event fired when the window is resized
47
- */
48
- readonly Resize: IEvent;
49
80
  /**
50
81
  * event fired when the window breakpoint changes
82
+ *
83
+ * Use {@link BreakpointChangeListener} to handle this event
51
84
  */
52
85
  readonly BreakpointChange: IEvent;
86
+ /**
87
+ * event fired when the window is resized
88
+ *
89
+ * Use {@link ViewResizeListener} to handle this event
90
+ */
91
+ readonly Resize: IEvent;
53
92
  /**
54
93
  * Get the current breakpoint of the parent window
94
+ * @returns current breakpoint
55
95
  */
56
96
  getBreakpoint(): Promise<BreakPoint>;
57
97
  /**
58
98
  * Get the current viewport size of the parent window
99
+ * @returns viewport size
59
100
  */
60
101
  getViewPortSize(): Promise<ViewportSize>;
61
102
  }