Archive for February 2019

 

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 you are navigating to.

 

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

 

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:

 

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 out today Get the latest release of the @pnp/spfx-property-controls from npm by executing in the command line: npm i @pnp/spfx-property-controls -S -E.

 

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.

 

If you are working on a SharePoint Framework solution which has to support multiple languages. You will already know that the localized labels are created in localization (resource) files which are “just” JavaScript files. There is actually nothing wrong with this approach in SharePoint Framework, although you could experience some issues with it.