Skip to content

Configuration keys start with an int break manifest import #36

Description

@scrthq

Following up on SCRT-HQ/PSProfile#28

It looks like PowerShell doesn't like dictionary keys that start with an int and are not wrapped in quotes, resulting in the parser breaking when attempting to import metadata containing keys like this. Sample to replicate:

@{1BadKey = 'Value'}

image

Digging into this and sending over a PR asap!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions