Since the SharePoint Framework v1.2.0 release; it is now possible to let your custom property pane fields trigger the apply button in non-reactive property panes. Before this release, you had to implement your own logic to re-render the contents of your web part or use the reactive property pane. ## So, what changed? In the previous versions, the **onRender** method of your
Some time ago I wrote a couple of articles about how you can automate the process of releasing your SharePoint Framework solutions. This was achieved by two custom Gulp tasks to upload the [static assets](https://www.eliostruyf.com/automate-publishing-of-your-sharepoint-framework-scripts-to-office-365-public-cdn/) and [solution package](https://www.eliostruyf.com/automate-sharepoint-framework-solution-package-deployment/) and a complete [Visual Studio Team Services build and release pipeline](https://www.eliostruyf.com/configure-a-build-and-release-pipeline-for-your-sharepoint-framework-solution-deployments/). This process already saved me a lot of time, but since some
When SharePoint 2013 got released there was something missing in the UI. There was no breadcrumb control anymore like in SharePoint 2010. A couple of clients and users were struggling finding their way on the site. In March 2013, I created a script that allowed you to transform the SharePoint text in the suite bar (on the left side) into
With the latest release of the SharePoint Framework generator, they introduced extensions. These extensions provide you a way to extend the modern site experience in SharePoint. You can, for example, add your own headers and footers, override how fields are rendered and create some custom list actions. In this article, I will focus on how you can use the **ListView Command
Since I wrote the article about how you could configure build and release pipelines in Visual Studio Team Services, I got a couple of people asking if it is possible to get different builds working on one tenant. When you build something with the SharePoint Framework and are ready to move from development (workbench) to test or production. You have to
If you ever created Gulp tasks which made use of arguments to specify certain configuration settings to be used during the execution. You probably made use of a module called [yargs](https://www.npmjs.com/package/yargs). The yargs module makes it easy to check if arguments are provided and to retrieve their values. If you are building your own custom Gulp tasks for your SharePoint Framework projects,
Let's build together
Manage content in VS Code
Present from VS Code
Engage with your audience throughout the event lifecycle
