You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain toast messages cause an error until server restart
Steps To Reproduce
New-PodeWebSelect -Name 'SQLServer:' -Options @($Servers) | Register-PodeWebEvent -Type Click -ScriptBlock {Show-PodeWebToast -Title "Unsupported" -Icon "message-alert-outline" -Message "This value is hard-coded to SPN-SC1D-SQL.nacloud.ecihosting.com for this example"}
Expected Behavior
Toast message wouldn't update unit the next restart, but it shouldn't produce an error.
Screenshots
Platform
OS: Windows Server 2019 Standard
Browser: Edge Version 130.0.2849.46
Versions:
Pode: v2.9.0
Pode.Web v0.8.3
PowerShell v7.4.5
Additional Context
I noticed this issue when I changed the name of the server from "SCN-SC1-CVSQL1" to "SPn-SC1d-SQL.NACloud.ecihosting.com"
I'm guessing based on the error message and the reference to Utilities.ps1 lines ~530 that the issue has to do with the periods in the message. It seems to work fine once the server restarts, but I thought it was weird enough to look into.
The text was updated successfully, but these errors were encountered:
Describe the Bug
Certain toast messages cause an error until server restart
Steps To Reproduce
New-PodeWebSelect -Name 'SQLServer:' -Options @($Servers) | Register-PodeWebEvent -Type Click -ScriptBlock {Show-PodeWebToast -Title "Unsupported" -Icon "message-alert-outline" -Message "This value is hard-coded to SPN-SC1D-SQL.nacloud.ecihosting.com for this example"}
Expected Behavior
Toast message wouldn't update unit the next restart, but it shouldn't produce an error.
Screenshots
Platform
Additional Context
I noticed this issue when I changed the name of the server from "SCN-SC1-CVSQL1" to "SPn-SC1d-SQL.NACloud.ecihosting.com"
I'm guessing based on the error message and the reference to Utilities.ps1 lines ~530 that the issue has to do with the periods in the message. It seems to work fine once the server restarts, but I thought it was weird enough to look into.
The text was updated successfully, but these errors were encountered: