tag:blogger.com,1999:blog-3066084330774405472.post6044219796498671200..comments2019-09-11T08:57:09.704-07:00Comments on Tricky SharePoint: React Templates Using SPFx Library Components. Part II. Implementation.Alex Terentievhttp://www.blogger.com/profile/07845409434432102100noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3066084330774405472.post-34947804266777529122019-09-03T09:18:18.110-07:002019-09-03T09:18:18.110-07:00Hey!
Yes, I think for such a situation additional ...Hey!<br />Yes, I think for such a situation additional method in the contract would be good implementation.Alex Terentievhttps://www.blogger.com/profile/07845409434432102100noreply@blogger.comtag:blogger.com,1999:blog-3066084330774405472.post-10368850069465706802019-09-02T07:18:08.105-07:002019-09-02T07:18:08.105-07:00Hey this was a great read! I&#39;m curious how you...Hey this was a great read! I&#39;m curious how you would handle the situation where different templates have different web part property configurations. Ex: We want to allow the user to configure than PanelSize of the TaskDetails template. Would you just expand your &quot;contract&quot; so that in addition to a React compononent, you also return something like &quot;getPropertyPaneGroups()&quot;?AndrewPetersen_Film201https://www.blogger.com/profile/13390678355781468817noreply@blogger.com