Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Nov 25, 2025

The README lacked concrete examples of how to configure multiple emitter options, showing only a placeholder option: value. Custom emitter authors also need guidance on using their own emitter name in options.

Changes

  • Added command-line example with multiple --option flags
  • Updated YAML config example with real option names/values
  • Added note for custom emitter authors about specifying their emitter name

Example

Command line:

tsp compile . --emit=@typespec/http-client-csharp \
  --option "@typespec/http-client-csharp.package-name=MyClient" \
  --option "@typespec/http-client-csharp.generate-protocol-methods=false"

YAML config:

emit:
  - "@typespec/http-client-csharp"
options:
  "@typespec/http-client-csharp":
    package-name: MyClient
    generate-protocol-methods: false
    generate-convenience-methods: true
Original prompt

This section details on the original issue you should resolve

<issue_title>Add full example that uses multiple options</issue_title>
<issue_description>In the docs, we should make it clear how to pass options by showing a full command that uses multiple emitter options.

We should also highlight that custom emitters need to specify their emitter name in the options.</issue_description>

Comments on the Issue (you are @copilot in this section)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI changed the title [WIP] Add full example showing multiple options usage Add full example that uses multiple options to http-client-csharp README Nov 25, 2025
Copilot AI requested a review from JoshLove-msft November 25, 2025 04:26
Copilot finished work on behalf of JoshLove-msft November 25, 2025 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add full example that uses multiple options

2 participants