Skip to content

Mapped Network Path glob pattern does not recognize backslashes or drive letter or network path #1173

@ZBB-XD

Description

@ZBB-XD

Describe the bug

On windows cant specify any amount of mapped network path as the glob pattern using backslashes (\\). It also doesnt accept drive letter paths even with forward slashes. it also doesnt recognize the full network path, even with forward slashes.

Expected Behavior

I get auto complete on a yaml thats on the network drive

Current Behavior

it doesnt

Steps to Reproduce

  1. map a network path to a drive letter, for example map //network.com/path to "J:"
  2. put a yaml file AND a yaml schema on that path
  3. in vs code's yaml.schemas workspace setting, put "J:\\full\\path\\to\\schema.json":"J:\\full\\path\\to\\file.yaml"
  4. it doesnt work. Any combination I tried of full pathing and wildcards in step 3 doesnt work. even stuff like "\\*" If I swap to forward slashes, then wildcard paths work but the full path still does not unless I remove the network drive letter for a wildcard.

So to recap, glob patterns things that should work but do not:

"J:\\full\\path\\to\\file.yaml",
"J:\\*\\path\\to\\file.yaml"
"*\\file.yaml"
"J:/full/path/to/file.yaml"
"//network.com/path/to/file.yaml"
"\\\\network.com\\path\\to\\file.yaml"

What I have to do instead is some variation on this using wildcards as needed:

"*/full/path/to/file.yaml"

Environment

  • [X ] Windows
  • Mac
  • Linux
  • other (please specify)

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