Today Microsoft announced new updates coming to the SharePoint Framework ahead of their sessions at the Build Conference. In a blog post, Build integrated user experiences with new capabilities of SharePoint and OneDrive , they talked about four big additions that engineering is working on and will make it into a new developer preview of the SharePoint Framework by the end of May 2017.
All of these things are developed & deployed using the same SharePoint Framework process including the build toolchain and, Yeoman generator and client side development characteristics.
I’m eager to play with the developer preview and see what is possible. What I like about these additions is they bring some highly useful features we had in previous SharePoint development models like solutions and add-ins to the SharePoint Framework.
JSLink field customizers, you can change what’s rendered in a cell based on the data within the cell. For instance, maybe you want to render a KPI visualization based on the number value within the cell. With field customizers, you can easily implement some field rendering override to implement this.
These aren’t really
div elements on the page, such as headers and footers.
Using application customizers would allow us to create custom headers and footers or use it to do something such as add Azure App Insights or Google Analytics to all pages within a SharePoint site.
The third type of artifact they are adding to the SharePoint Framework are command sets which we knew as custom actions . Using a command set, the SPFx now allows us to add items to the ECB menu (the drop-down context menu on list and library items) as well as buttons to list and library toolbars.
custom actions command sets again.
Similar to a capability we have had for many years in SharePoint, SPFx brings the notion of web part connections to SPFx client-side web parts. It works very much the same way we did it before. You define some sort of an object, such as an interface, and then create two different web parts: a consumer and a producer.
The producer will raise an event through the SPFx’s shared context. The event has a specific name and will pass the information along the event bus that conforms to a specific object / interface.
The consumer will subscribe to the event by name. When an event is published, the SPFx will handle the communication between the producer and consumer of the two web parts.
These connected web parts are great when you want to implement some sort of a master-detail view or filtering capabilities with multiple web parts on the page at once.
Looks like a developer preview of these new features will roll out soon.