Changing culture settings is not taken into account in the PowerShell Extension's PowerShell instance

Offen
#4,770 8 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@andyleejordan arbeitet bereits daran.

Seit 11.10.2023.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

Issue-Bug
Prerequisites
  • I have written a descriptive issue title.
  • I have searched all open and closed issues to ensure it has not already been reported.
  • I have read the troubleshooting guide.
  • I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
  • I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
  • If this is a security issue, I have read the security issue reporting guidance.
Summary

Changing the culture's settings such as the time format has no effect in the PowerShell Extension:

image

PowerShell Version
PSVersion                      7.3.7
PSEdition                      Core
GitCommitId                    7.3.7
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
Visual Studio Code Version
1.82.2
abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
x64
Extension Version
ms-vscode.powershell@2023.9.4
TylerLeonhardt.vscode-inline-values-powershell@0.0.7
Steps to Reproduce

From the PowerShell Extension's PowerShell prompt, run the following script:

    # derived from https://github.com/PowerShell/PowerShell/issues/19536#issuecomment-1515140128
    # Save the original culture.
    $global:originalculture = [cultureinfo]::CurrentCulture

    # Temporarily replace it with a read/write copy.
    [cultureinfo]::CurrentCulture = [cultureinfo] $global:originalculture.Name


    # Modify the LongTimePattern format to include milliseconds.
    [cultureinfo]::CurrentCulture.DateTimeFormat.LongTimePattern += ([cultureinfo]::CurrentCulture.NumberFormat.CurrencyDecimalSeparator + 'fff')

This has no effect to e.g. the output from Get-Date:

PS> Set-LongTimePatternToIncludeMilliseconds.ps1
PS> Get-Date

Saturday, September 30, 2023 12:23:05

Whereas the result is correct in a "normal" PowerShell instance:

PS> Set-LongTimePatternToIncludeMilliseconds.ps1
PS> get-date

Saturday, September 30, 2023 12:24:17.297
Visuals

No response

Logs

No response

Vorherrschende Sprache
TypeScript
Sterne
1.9k
Forks
548
Keine gemergten PRs in 30 T.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus PowerShell/vscode-powershell

Alle Issues in PowerShell/vscode-powershell

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.