Importing PowerHTML module in a directory with a Types folder containing multiple .ps1xml files fails #8

Activity

1. forevanyeung commented on Oct 16, 2022

   

   forevanyeung

   on Oct 16, 2022

   Author

   More actions

   Submitted a PR that removes the wildcard matching in FormatsToProcess which fixes the problem.

   Another alternative that will dynamically update format data for all files in the Types folder is adding the below code to the psm1 file.

   #Append format data to session
   $ModuleFormats = @( Get-ChildItem -Path $PSScriptRoot\Types\*.ps1xml -ErrorAction SilentlyContinue )
   foreach ($t in $ModuleFormats)
   {
       Write-Verbose "Appending format data: $($t.FullName)"
       Update-FormatData -Append $t
   }
   

   However, during my testing, this does not clean up after removing the module. So I opted to go for statically defining the format files.

   PS /Users/evan.yeung/git/PowerHTML> get-formatdata | Where-Object { $_.TypeNames -like "*HtmlAgilityPack*" }
   PS /Users/evan.yeung/git/PowerHTML> import-module ../../git/PowerHTML/
   PS /Users/evan.yeung/git/PowerHTML> get-formatdata | Where-Object { $_.TypeNames -like "*HtmlAgilityPack*" }
   
   TypeNames                         FormatViewDefinition
   ---------                         --------------------
   {HtmlAgilityPack.HtmlNode}        {HtmlAgilityPack.HtmlNode}
   {HtmlAgilityPack.HtmlTextNode}    {HtmlAgilityPack.HtmlNode}
   {HtmlAgilityPack.HtmlCommentNode} {HtmlAgilityPack.HtmlNode}
   
   PS /Users/evan.yeung/git/PowerHTML> remove-module powerhtml
   PS /Users/evan.yeung/git/PowerHTML> get-formatdata | Where-Object { $_.TypeNames -like "*HtmlAgilityPack*" }
   
   TypeNames                         FormatViewDefinition
   ---------                         --------------------
   {HtmlAgilityPack.HtmlNode}        {HtmlAgilityPack.HtmlNode}
   {HtmlAgilityPack.HtmlTextNode}    {HtmlAgilityPack.HtmlNode}
   {HtmlAgilityPack.HtmlCommentNode} {HtmlAgilityPack.HtmlNode}