diff --git a/src/frontend/.starlight-icons/safelist.json b/src/frontend/.starlight-icons/safelist.json index 8b9037434c..20f8fa07f8 100644 --- a/src/frontend/.starlight-icons/safelist.json +++ b/src/frontend/.starlight-icons/safelist.json @@ -40,8 +40,11 @@ "i-material-icon-theme:folder-src-open", "i-material-icon-theme:folder-template", "i-material-icon-theme:folder-template-open", + "i-material-icon-theme:folder-vscode", + "i-material-icon-theme:folder-vscode-open", "i-material-icon-theme:git", "i-material-icon-theme:go", + "i-material-icon-theme:go-mod", "i-material-icon-theme:gradle", "i-material-icon-theme:html", "i-material-icon-theme:http", diff --git a/src/frontend/src/content/docs/app-host/go-apphost.mdx b/src/frontend/src/content/docs/app-host/go-apphost.mdx index 9d4a8cb2ec..73b4c10ac3 100644 --- a/src/frontend/src/content/docs/app-host/go-apphost.mdx +++ b/src/frontend/src/content/docs/app-host/go-apphost.mdx @@ -197,6 +197,10 @@ The SDK regenerates when: The starter's `.gitignore` already lists `.aspire/`. The directory holds generated files that the CLI recreates from `aspire.config.json`, so keep it out of source control. ::: +### Documentation in the SDK + +The generated `aspire.go` includes godoc comments, so `go doc` and editor hover (gopls) show each API's summary, parameters, and return value. Obsolete APIs carry a `Deprecated:` notice that gopls and staticcheck flag, and experimental APIs are marked with an **Experimental** heading. + ### Restore the SDK Run `aspire restore` to regenerate the SDK without starting the AppHost: diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx index 9b11c6b323..0b50b6a6e7 100644 --- a/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx +++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx @@ -53,11 +53,7 @@ The destroy command requires --yes when the --non-interactive option is specifie ### Unknown arguments -`aspire destroy` rejects unrecognized options and positional arguments before it discovers or starts the AppHost, so a mistyped option can't silently run the destroy pipeline. The command exits with code `1`: - -```bash title="Aspire CLI" -aspire destroy --force -``` +`aspire destroy` rejects unrecognized options and positional arguments before it discovers or starts the AppHost, so a mistyped option can't silently run the destroy pipeline. For example, passing `--force`, which isn't an `aspire destroy` option, exits with code `1` and reports: ```text title="Output" Unrecognized command or argument '--force'.