Closed kevmcdonk closed 3 years ago
Adding @PaoloPia , @erwinvanhunen for awereness
@kevmcdonk : sorry for the late reply, but yes we would love to see a PR bringing the template to markdown documentation feature. This can be a super useful feature for customers more easily see what's inside a template and document it.
Working on it in a branch and you can see an example of how the output is looking at https://github.com/cpsglobal/pnpframework/blob/dev/docs/ProvisioningExportMarkdownSample.md. Site Columns looking good. Content Types and List Instances need work to make them look more like you would see from the settings in SharePoint themselves.
I've just submitted a PR for this. To be truly useful, it will need updates to PnP PowerShell but I'm keeping them as two different steps for now.
Thanks @kevmcdonk , @erwinvanhunen merged your PR here and already started working on an integration in the PnP PS cmdlets. Thanks for this great PR.
I've got a bit of working code for PnP. Only issue was that it needed the reference to the updated version before I could do a PR. Do you want me to submit it?
Don't think that's needed at this point, if so I'll let you know.
I've been looking at a way to get a friendly way of viewing a PnP template as a document of a site. After trying out a few ways of manipulating the XML but feel that getting it out as a TemplateProvider would be a great way and then have pnppowershell allowing .md files as an -Out format.
Before I go too far down that path of that in a fork, would that likely to be accepted as a PR?
I am thinking of having a set of Writers similar to the XmlSerializers that would build up a TextWriter object. That would then be pushed out in the stream for ToFormattedTemplate.