0.10.29.160

PSFramework/PSFramework.psd1

@@ -5,7 +5,7 @@
 	RootModule = 'PSFramework.psm1'
 
 	# Version number of this module.
-	ModuleVersion = '0.10.28.144'
+	ModuleVersion = '0.10.29.160'
 
 	# ID used to uniquely identify this module
 	GUID = '8028b914-132b-431f-baa9-94a6952f21ff'
@@ -66,6 +66,7 @@
 		'Clear-PSFResultCache',
 		'ConvertFrom-PSFClixml',
 		'ConvertTo-PSFClixml',
+		'ConvertTo-PSFHashtable',
 		'Disable-PSFTaskEngineTask',
 		'Enable-PSFTaskEngineTask',
 		'Export-PSFClixml',
@@ -75,17 +76,21 @@
 		'Get-PSFDynamicContentObject',
 		'Get-PSFMessage',
 		'Get-PSFLicense',
+		'Get-PSFLocalizedString',
 		'Get-PSFLoggingProvider',
 		'Get-PSFMessageLevelModifier',
+		'Get-PSFPipeline',
 		'Get-PSFResultCache',
 		'Get-PSFRunspace',
+		'Get-PSFScriptblock',
 		'Get-PSFTaskEngineCache',
 		'Get-PSFTaskEngineTask',
 		'Get-PSFTypeSerializationData',
 		'Get-PSFUserChoice',
 		'Import-PSFClixml',
 		'Import-PSFCmdlet',
 		'Import-PSFConfig',
+		'Import-PSFLocalizedString',
 		'Install-PSFLoggingProvider',
 		'Invoke-PSFCommand',
 		'New-PSFLicense',
@@ -110,6 +115,7 @@
 		'Set-PSFDynamicContentObject',
 		'Set-PSFLoggingProvider',
 		'Set-PSFResultCache',
+		'Set-PSFScriptblock',
 		'Set-PSFTaskEngineCache',
 		'Set-PSFTeppResult',
 		'Set-PSFTypeAlias',

PSFramework/PSFramework.psm1

@@ -53,8 +53,12 @@ function Import-ModuleFile
 		$Path
 	)
 
-	if ($doDotSource) { . (Resolve-Path $Path) }
-	else { $ExecutionContext.InvokeCommand.InvokeScript($false, ([scriptblock]::Create([io.file]::ReadAllText((Resolve-Path $Path).ProviderPath))), $null, $null) }
+	try
+	{
+		if ($doDotSource) { . (Resolve-Path $Path) }
+		else { $ExecutionContext.InvokeCommand.InvokeScript($false, ([scriptblock]::Create([io.file]::ReadAllText((Resolve-Path $Path).ProviderPath))), $null, $null) }
+	}
+	catch { throw (New-Object System.Exception("Failed to import $(Resolve-Path $Path) _ $_", $_.Exception)) }
 }
 
 #region Load individual files

PSFramework/The PSFramework Reliability Promise.md

@@ -1,4 +1,4 @@
-# The PSFramework Reliability Promise
+# The PSFramework Reliability Promise
 ## About
 
 The PSFramework is designed as a platform for others to build their code upon.
@@ -33,18 +33,18 @@ Now what is covered by this promise:
 
  - All functions and cmdlets signatures. Any current parameterization will keep being valid and produce the same result.
  - All logging providers. Configuration and default behavior cannot be changed.
- - All parameter classes will keep understanding current input (they may _also_ learn new things however)
- - All validation attributes will keep accepting the current definition (new definitions may be introduced however)
+ - All parameter classes will keep understanding current input (they may _also_ learn to understand new input)
+ - All validation attributes will keep accepting the current definition (but new definitions may be introduced)
  - Any otherwise advertised feature on the [documentation site](https://psframework.org/documentation/documents/psframework.html)
 
 Not covered by this promise:
 
  - Preview features. All new commands that are being released are considered to be in preview for one month. This is designed to allow for initial user feedback to be implemented. Note: This only applies to the initial command release, _not_ to any later updates that were made after the preview stage was over.
- - Any other internal library mechanics. Some of them need to be public for script funtions to access them. That does _not_ imply they are for public consumption (You may use them for that, but at your own risk).
+ - Any other internal library mechanics. Some of them need to be public for script functions to access them. That does _not_ imply they are for public consumption (You may use them for that, but at your own risk).
  - UI User Interaction. Messages written to the host intended for a human consumption may be changed in how they are being displayed. The previous state however must be available using configuration (thus changes to the _default_ behavior can be made, as long as the old state can be reintroduced).
  - Experimental features. Any feature listed as experimental below is considered to be exempt from this policy.
  - System mandated change: If a feature needs to be adapted in order for it to be operable on all supported platforms (for example an active conflict with PowerShell Core), then that is an overriding technical need to change it.
- - A feature undergong the Process of Change.
+ - A feature undergoing the Process of Change.
 
 ## Process of Change