Azure / Office 365 / SharePoint Development / Search
The reason you probably read this post is that you already wrote some unit tests for SharePoint Framework projects and you stumble upon a problem and want to debug one of your unit-tests. Apparently, the process is not so easy as linking your debugger to the gulp test task. There is a bit more plumbing...Read More →
In one of the previous posts I showed that since SharePoint Framework version 1.2.0, code coverage reports were added. When you run the gulp test task, it will execute the tests, and generate a code coverage report which you can find under the temp/coverage/js project folder. Read more about this in the following article: SharePoint Framework...Read More →
Based on the number of questions I receive in my mailbox, I can see that display templates are still not yet forgotten. A long time ago, I wrote about how to correctly include scripts into your display templates. Read more: Correctly including scripts into your display templates The main issue when using the default functions...Read More →
A while ago I wrote an article about writing unit tests for your SharePoint Framework components. One of the missing things was a code coverage report to check how well you unit-test your codebase. Read more: Writing unit-tests for your SharePoint Framework components Apparently, with the v1.2.0 of SharePoint Framework they added a tool called...Read More →
One of the new things in the latest releases is the functionality to bundle multiple components into a single JavaScript bundle file. Quote: Multi-component bundles can make it easier to share code and logic across similar components, as well as reduce the overall size of your JavaScript since you only get one instance of the...Read More →
