Trying to understand how winget export works with additional dsc ressources.

Hi,

I was simply trying to export my vscode setup together with the list of extensions I have installed.

This is basically what I am doing.

install-module vscode
winget configure export --Package-Id Microsoft.VisualStudioCode -o .\VsCodeExport.winget --module vscode --resource vscodeextension

And this is what the file VsCodeExport.winget looks like

# Created using winget configure export 1.12.350
# yaml-language-server: $schema=https://aka.ms/configuration-dsc-schema/0.3
$schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/config/document.json
metadata:
  winget:
    processor:
      identifier: "dscv3"
resources:
- name: winget_Microsoft.VisualStudioCode
  type: Microsoft.WinGet/Package
  metadata:
    description: "Install Microsoft.VisualStudioCode"
  properties:
    id: "Microsoft.VisualStudioCode"
    source: "winget"
    

I am missing the vscode extension part. I am unsure if I am doing something wrong, is that actually supported, or if there is a bug.

Unfortunatly, I couldn't find that many ressources on winget export :(

Start by reproducing the shown install-module vscode and winget configure export command, then inspect the generated VsCodeExport.winget file. Determine whether the vscodeextension resource is supported and why the export contains only the Microsoft.VisualStudioCode package. Done means documenting the expected behavior or identifying a specific fix location.