PowerShell / PowerShell/DSC

Problems loading reference while authoring resource manifest

Open
#757 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Doc-Impact Issue-Bug Need-Review
Dominant language
Rust
Stars
523
Forks
75
Avg merge
3d 16h
Merged PRs (30d)
24

Description

Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.
Summary

I am experiencing issues while authoring a resource manifest. Whenever defining the URL shortener: https://aka.ms/dsc/schemas/v3/bundled/resource/manifest.json, the manifest.export.json file cannot be loaded.

Image

Changing this to: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/v3/bundled/resource/manifest.json helps me with the IntelliSense features in VSCode.

Steps to reproduce
  1. Create a test.dsc.resource.json file
  2. Add "$schema": "https://aka.ms/dsc/schemas/v3/bundled/resource/manifest.json"

The warning appears.

Expected behavior
All file references are loaded.
Actual behavior
Not all file references are loaded, breaking some IntelliSense features.
Error details

Environment data
Name                           Value
----                           -----
PSVersion                      7.4.7
PSEdition                      Core
GitCommitId                    7.4.7
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
Version

3.0.2

Visuals

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the warning with test.dsc.resource.json using the aka.ms schema URL, then compare its loading with the raw GitHub URL and inspect the referenced manifest.json and manifest.export.json. Done means all file references load and the affected VS Code IntelliSense features work without the warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.