You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Release notes for the SharePoint Framework v1.14 release
4
-
ms.date: 2/10/2022
4
+
ms.date: 2/17/2022
5
5
ms.prod: sharepoint
6
6
ms.localizationpriority: high
7
7
---
8
8
# SharePoint Framework v1.14 release notes
9
9
10
10
There will be multiple public preview release using the **@next** tag in the [NPMJS.org](https://www.npmjs.org) registry before final release candidates and a final public release.
### Adaptive Card Extension updates for Viva Connections
44
+
45
+
#### Updated the ACE scaffolding for Viva Connections
48
46
49
-
For improved performance, SharePoint Framework now supports local caching of your Adaptive Card Extension's card views. The cached card view will be immediately rendered when loading your Adaptive Card Extension. After Adaptive Card Extension loads, it can optionally update the card view.
47
+
Updated Adaptive Card Extensions scaffolding to be more succinct.
48
+
49
+
#### Get Current ViewNavigator for Adaptive Card Extension
50
50
51
51
```typescript
52
-
interface ICacheSettings {
53
-
/**
54
-
* Whether cache is enabled. Default: true
55
-
*/
56
-
isEnabled: boolean;
57
-
/**
58
-
* Expiry time in seconds. Default: 86400 seconds (24 hours)
59
-
*/
60
-
expiryTimeInSeconds: number;
61
-
62
-
/**
63
-
* Returns the Card View used to generate the cached card.
64
-
* By default, the currently rendered Card View will be used to cache the card.
By default caching is enabled with default settings. An Adaptive Card Extension can customize its
72
-
cache settings by overriding `getCacheSettings` to return the settings it wants to override.
55
+
If the current `renderType` is `Card` then returns `BaseAdaptiveCardExtension.cardNavigator`. If the current `renderType` is `QuickView` then returns `BaseAdaptiveCardExtension.quickViewNavigator`.
73
56
74
-
When the last known card view shouldn't be cached, you can provide a specific card view to be
75
-
cached and displayed on the next page load through `ICacheSettings.cachedCardView`. This card view
76
-
doesn't need to have been previously registered.
57
+
### List View Command Set Updates
77
58
78
-
An Adaptive Card Extension can also locally cache its current state. By default no state is cached.
Initial state of the Adaptive Card Extension can be seeded from the cached state. The cached state can also be used to determine if any further logic needs to be executed.
86
+
This event gets raised every time the list view state changes. The arguments contain type of occured event (see `ListViewAccessorStateChanges`) and previous state of the list view (see `IListViewAccessorState`).
98
87
99
-
State caching and the cache expiry time can be used to determine when
100
-
expensive remote calls need to be made by the Adaptive Card Extension.
88
+
#### List Command Set Command Disabled Property
101
89
102
-
Caching can help significantly improve the perceived performance for your Adaptive Card Extension.
90
+
```typescript
91
+
Command.disabled: boolean|undefined;
92
+
```
93
+
94
+
### Web Part specific updates
103
95
104
-
### Web Part lifecycle method for theme changes
96
+
#### Predefined Web Part Picker Group for Web Parts in Development
When a theme is initialized or changed on a page, `onThemeChanged` will be invoked with the new theme.
119
+
When a theme is initialized or changed on a page, `onThemeChanged` will be invoked with the new
120
+
theme.
111
121
112
-
> [!NOTE]
122
+
> [!IMPORTANT]
113
123
> `render` should not be invoked in `onThemeChanged`. Calling `render` can lead to unpredicted re-flow of the web part. `render` will automatically be invoked if needed.
114
124
115
-
### Detect if a component is loading from localhost
125
+
#### Updated Web Part Templates
126
+
127
+
- No Framework, and React templates are updated with new user-friendly UI
128
+
- New "Minimal" template is added: allows to start development with the minimal amount of code provisioned.
129
+
130
+
### Other generic updates and changes
131
+
132
+
#### Changes to Scaffolding Options and Prompts
133
+
134
+
The next propmts were deprecated in favor to their defaults:
135
+
136
+
- Solution description
137
+
- Environment (SharePoint) version
138
+
- Tenant-wide deployment
139
+
- Isolated permissions
140
+
- Component description
141
+
142
+
#### Detect if a component is loading from localhost
Any SPFx component can now check if it's currently running from code served locally.
122
149
123
-
### Hide a Property Pane group name
150
+
####Hide a Property Pane group name
124
151
125
152
```typescript
126
153
IPropertyPaneGroup.isGroupNameHidden?:boolean;
127
154
```
128
155
129
-
`isGroupNameHidden` can be used to skip the rendering of the Property Pane group name to avoid an empty group header being displayed.
156
+
`isGroupNameHidden` can be used to skip the rendering of the Property Pane group name to avoid an
157
+
empty group header being displayed.
130
158
131
159
The default value of `isGroupNameHidden` is false.
132
160
133
-
### Updated Web Part Templates
161
+
#### ipAddress Property in serve.json
162
+
New property `ipAddress` has been added to `serve.json` configuration. This parameter is helpful when using Docker containers. For example, to set the serve host as '0.0.0.0'.
163
+
This property will be explicitly used to wind up the server, meaning all debug URLs and webpack configurations will not be affected.
134
164
135
-
- No Framework, and React templates are updated with new end-user friendly UI for SharePoint and Microsoft Teams with theme detection, section background color support and more.
136
-
- New "Minimal" template is added: allows to start development with the minimal amount of code provisioned.
165
+
## Preview Features and Capabilities
166
+
167
+
Following features are still in preview status as part of the 1.14 release and should not be used in production. We are looking into releasing them officially as part of the upcoming 1.15 release.
168
+
169
+
### Adaptive Card Extensions card view caching
137
170
138
-
### Get Current ViewNavigator for Adaptive Card Extension
171
+
For improved performance, SPFx now supports local caching of your Adaptive Card Extension's
172
+
card views. The cached card view will be immediately rendered when loading your Adaptive Card
173
+
Extension. After your Adaptive Card Extension loads, it can optionally update the card view.
139
174
140
175
```typescript
141
-
BaseAdaptiveCardExtension.navigator
176
+
interfaceICacheSettings {
177
+
/**
178
+
* Whether cache is enabled. Default: true
179
+
*/
180
+
isEnabled:boolean;
181
+
/**
182
+
* Expiry time in seconds. Default: 86400 seconds (24 hours)
183
+
*/
184
+
expiryTimeInSeconds:number;
185
+
186
+
/**
187
+
* Returns the Card View used to generate the cached card.
188
+
* By default, the currently rendered Card View will be used to cache the card.
If the current `renderType` is `Card` then returns `BaseAdaptiveCardExtension.cardNavigator`. If the current `renderType` is `QuickView` then returns `BaseAdaptiveCardExtension.quickViewNavigator`.
195
+
By default caching is enabled with default settings. An Adaptive Card Extension can customize its
196
+
cache settings by overriding `getCacheSettings` to return the settings it wants to override.
145
197
146
-
#### Error Handler Method. This method will be invoked when an Action throws an error.
198
+
When the last known card view shouldn't be cached, you can provide a specific card view to be
199
+
cached and displayed on the next page load through `ICacheSettings.cachedCardView`. This card view
200
+
doesn't need to have been previously registered.
201
+
202
+
An Adaptive Card Extension can also locally cache its current state. By default no state is cached.
Your Adaptive Card Extension's initial state can be seeded from the cached state. The cached state can also be used to determine if any further logic needs to be executed.
222
+
223
+
State caching and the cache expiry time can be used to determine when expensive remote calls need to be made by the Adaptive Card Extension.
224
+
225
+
Caching can help significantly improve the perceived performance for your Adaptive Card Extension.
226
+
227
+
### Error Handler Method. This method will be invoked when an Action throws an error
Override this method to handle errors from Adaptive Card actions.
153
234
154
-
### New Action types for media and geolocation.
235
+
### New Action types for media and geolocation
155
236
156
237
> [!NOTE]
157
238
> These new actions are **only available in the browser** currently. Viva Connections desktop and Viva Connections mobile support will be enabled later.
@@ -165,6 +246,7 @@ Get Location | Not Supported | Supported | Supported
165
246
Show Location | Not Supported | Supported | Supported
166
247
167
248
```typescript
249
+
168
250
ISPFxAdaptiveCard.actions?: (
169
251
|ISubmitAction
170
252
|IOpenUrlAction
@@ -189,7 +271,7 @@ The SelectMedia and Location action can be configured as shown below:
189
271
type: 'VivaAction.GetLocation',
190
272
id: 'Get Location',
191
273
parameters: {chooseLocationOnMap: true}
192
-
},
274
+
}
193
275
{
194
276
type: 'VivaAction.ShowLocation',
195
277
id: 'Show Location',
@@ -198,79 +280,23 @@ The SelectMedia and Location action can be configured as shown below:
198
280
]
199
281
```
200
282
201
-
### List View Command Set Updates
202
-
203
-
> [NOTE!]
204
-
> Although the APIs are added, the functionality may not be available on some tenants.
205
-
206
-
#### Inform ListView on Command Set Changes
207
-
208
-
```typescript
209
-
BaseListViewCommandSet.raiseOnChange: () =>void
210
-
```
211
-
212
-
Use this method to fire `onChange` event and initialize a reflow of the ListView.
283
+
The actions will be rendered as below
213
284
214
-
#### Expanded List View Accessor State
285
+
Location Action:
215
286
216
-
`ListViewAccessor` provides expanded state of the current list view. **New** state properties are listed below.
287
+

217
288
218
-
-`rows` - currently rendered rows in the list view.
219
-
-`selectedRows` - selected rows in the list view.
220
-
-`list` - basic information about the list rendered by the list view.
221
-
-`view` - basic information about the view rendered by the list view.
222
-
-`folderInfo` - folder information for the list view.
223
-
-`appliedFilters` - filters applied to the list view.
224
-
-`sortField` - sort field name.
225
-
-`sortAscending` - specifies whether the list view is sorted ascending or descending.
This event gets raised every time the list view state changes. The arguments contain type of occurred event (see `ListViewAccessorStateChanges`) and previous state of the list view (see `IListViewAccessorState`).
291
+

234
292
235
-
#### List Command Set Command Disabled Property
236
-
237
-
```typescript
238
-
Command.disabled: boolean|undefined;
239
-
```
240
-
241
-
### Predefined Web Part Picker Group for Web Parts in Development
Use `clearDomElementCallback` to clear the DOM node.
257
-
258
-
### ipAddress Property in serve.json
259
-
260
-
New property `ipAddress` has been added to `serve.json` configuration. This parameter is helpful when using Docker containers. For example, to set the serve host as '0.0.0.0'.
261
-
This property will be explicitly used to wind up the server, meaning all debug URLs and webpack configurations won't be affected.
293
+
The Location Action can be used to get your current ___location, show your current or a custom ___location on a map, and choose your current ___location from a map. In the browser it uses Bing Maps as the mapping interface:
262
294
295
+

263
296
264
-
### Changes to Scaffolding Options and Prompts
297
+
The Select Media Action can be used to select Images from your native device. In the browser it uses the file picker to help access relavant files:
265
298
266
-
- New prompt for solution description is added.
267
-
- "Tenant-wide deployment" prompt is removed. The property is set to `true` by default and can be changed manually or using `skip-feature-deployment` argument.
268
-
- The next prompts were deprecated in favor to their defaults:
269
-
- Solution description
270
-
- Environment (SharePoint) version
271
-
- Tenant-wide deployment
272
-
- Isolated permissions
273
-
- Component description
299
+

0 commit comments