Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
SPFx Extension Placeholder Names Changed #805
Expected or Desired Behavior
The placeholder names for use with an Application Customizer have been PageHeader and PageFooter.
On modern pages within a developer tenant these are now Top and Bottom. However, modern list views are still reporting
Steps to Reproduce
To see the new placeholders, debug an Application Customizer on a modern page and add the following line to the
Are these changes part of the breaking changes promised with RC1 or are they an unplanned bug?
This is by design as part of moving closer to Release Candidate and GA. Due to numerous reasons, place holder names are changed and we'll need to update first server side before we can push out an update to the Yeoman templates. More information on upcoming updates will be available soon. We do apology the impact for your existing dev preview extensions.
I thought that might be the case, thanks for the update!
Honestly, I'm really excited about RC1 (and GA of course). It's just that I am giving a presentation tomorrow at SharePoint Saturday Charlotte on these. It didn't take much to rework my demos so far, but are there any other planned changes between now and tomorrow that I should be watching out for? Thanks!
referenced this issue
Aug 25, 2017
@thechriskent - you are actually in slightly dangerous waters. It really depends on which update cycle your tenant is. I would suggest to either take just in case screenshots or record a quick video as a back. Timing is not optimal and we hate to break early adopters, but there were some mandatory changes which were needed to be done. Changes are not huge, but the inconsistency between server and client can potentially cause you some challenges until our npm packages are published.
Right now we are pushing changes cross the tenants and farms. When this will hit your specific tenant is dependent on which farm it's hosted, so we can't define the exact date and time for each of the tenants. We'll provide more details and needed updates early next week. Place holder change won't be unfortunately the only change and some of the changes in upcoming RC will break you until you'll get the updated npm packages. Can't disclose unfortunately exact time on that right now, but will obviously happen soon with the needed details on updating your code.
If you have demos and/or presentations coming for example for this weekend, would recommend recording the demos beforehand to avoid issues and concentrate on the code presentation. We absolutely understand that this is not optimal for these situation and this only happens since it was developer preview - when we get to the GA, this kind of surprises will not happen.