Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature]: Expose advanced winapp pack options

Aperta
  • Qualcosa non va?
#322 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 8 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript, vscode
Ambito
desktop, developer-experience

Direzione di ricerca

Read the WinApp VS Code extension’s packaging flow and the CLI option definitions for pack; the issue does not name files or tests. Map each option to project mode or existing-build-output mode, then add the advanced command with validation and secure argument handling. Done means the selected options are summarized safely, CLI defaults are preserved, and documentation and tests cover the flow.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
Is your feature request related to a problem? Please describe.

The winapp CLI supports advanced pack options that are not currently surfaced by the WinApp VS Code extension. Users who need deterministic output paths, multi-targeted project selection, incremental packaging, existing certificates, or low-level package overrides must leave VS Code and invoke the CLI directly.

PR #309 adds MSIX bundle support and project-mode packaging, including project build configuration selection. Expanding that same PR to cover every advanced option would make its command flow and scope substantially larger.

Describe the solution you'd like

Add a dedicated advanced packaging experience, such as WinApp: Create MSIX Package With Options..., while keeping the default packaging command focused on common choices.

Evaluate and surface the remaining CLI options with source-aware applicability and validation:

  • --output
  • --framework
  • --no-build
  • --no-restore
  • repeatable --property <name=value>
  • --cert <path> and --cert-password
  • --name
  • --publisher
  • --manifest
  • --executable
  • --skip-pri

The advanced flow should:

  • show only options valid for project mode or existing-build-output mode
  • prompt only for values the user elects to override
  • validate .msix versus .msixbundle output names based on the selected packaging mode
  • define precedence when raw MSBuild properties overlap dedicated UI choices
  • avoid logging or displaying certificate passwords in the output channel or reconstructed command text
  • provide a summary/confirmation step before executing a complex command
  • preserve CLI defaults for options the user does not select
Additional context

Follow-up to #307 and draft PR #309. --configuration is intentionally not part of this issue because project build configuration selection is planned for #309.

The WinApp CLI already implements these options; this issue tracks the extension UX, validation, secure argument handling, documentation, and test coverage needed to expose them safely.

Lingua principale
TypeScript
Stelle
14
Fork
4
Merge medio
6g 14h
PR unite (30g)
8

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/WinAppVSCE

Tutte le issue di microsoft/WinAppVSCE

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.