When setting up a portal on SharePoint Online these days, you most likely will do it with a hub site driven approach. With hub sites, you have one root site collection, which can be seen as the parent, and all children are associated with it. Hub site association When building solutions for your hub sites, you probably need to know on which hub site your solution is currently running.
Version 1.14.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: Enhancements German translations added for attachment and RichText controls #333 SecurityTrimmedControl: Added a wrapper className property for the parent element #325 ListPicker: Add ability to filter the control via OData #319 IFrameDialog: closing dialog on commit #313 WebPartTitle add support for section background color #258 Fixes
Version 1.16.0 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: Enhancements PropertyFieldCollectionData: Add the ability for field validation to the custom fields #187 PropertyFieldCollectionData: Ability to provide custom labels for the save and cancel buttons #187 PropertyFieldListPicker: add ability to filter the control via OData #184 Fixes
When you need to support multiple languages for your SharePoint Framework solutions. It can be a hassle that you have to maintain each and every localization per component in their related loc folder. Official localization documentation: localize SharePoint Framework client-side web parts. Default component localization files If you have one component in your project, this is easy to maintain, but once you will have a couple more.
This will be a quick tip about a styling issue with the application customizers. If you are building application customizers that render something in the available top or bottom zones. It is recommended to add your own font styles. This might sound weird, but when you don’t do this, you might end up with styling differences between your pages.
When building a SharePoint Framework solution which includes application customizers. One of the important things about their functionality is how they behave during navigation events/page transitions. These days in modern SharePoint most of the page transitions are achieved from the client-side, which means that it does not fully reload the page, but only partially.