A new version of SharePoint Framework was just released and one of the great things is that some of the dependencies were bumped. In version SPFx version 1.8.0, TypeScript was updated to 2.7.2 and React to 16.7.0. The React version is not even so old; it was released in December 2018 and comes with some handy features like lazy loading
When developing solutions with SharePoint Framework it can happen that you need to navigate to another page from code. Normally in JavaScript or TypeScript this is very easy. All you have to do is set the new location like this: location.href = "<your-url>"; When you do this in SharePoint Framework, it has the side effect that it fully reloads the page
Version 1.12.0 of the SharePoint Framework React Controls (@pnp/spfx-controls-react) has been released. This is an open source library that shares a set of reusable React controls, which can be used in your SharePoint Framework solutions. This release includes the following changes: New control(s) ListItemAttachments: New control added #177 IFramePanel: New control added #226 Enhancements Added Russian localization #214 TaxonomyPicker: Ability to specify term actions #237 Fixes TaxonomyPicker: Terms are
Something that is giving me some trouble for a long time is that the SharePoint Framework build process treads warnings as errors in production builds (when the —ship flag is present). Let’s start by giving some background information. During bundling/packaging of your SharePoint Framework solution, you could see two types of messages: Warnings Errors
Version 1.14.1 of the SharePoint Framework Property Controls (@pnp/spfx-property-controls) has been released. This is an open source library that shares a set of reusable property pane controls, which can be used in your SharePoint Framework solutions. This release includes the following changes: Fixes TaxonomyPicker: Terms are sorted incorrectly under the wrong parent #153 EnterpriseTermPicker: Terms are sorted incorrectly under the wrong parent #156 Try it
When building custom gulp tasks in your SharePoint Framework solutions, it might be handy to log as the default build system does. More information about building custom gulp tasks can be found here: Integrate gulp tasks in SharePoint Framework toolchain When you would use the default console.log, console.warn,** **or console.error methods like this: They will just log as follows:
Let's build together
Manage content in VS Code
Present from VS Code
