Template for setting up an emitter #2736
Conversation
|
Changes in this PR will be published to the following url to try(check status of TypeSpec Pull Request Try It pipeline for publish status): Website: https://tspwebsitepr.z22.web.core.windows.net/prs/2736/ |
…rin/typespec into feature/library-init
timotheeguerin
requested review from
bterlson,
daviwil,
markcowl and
allenjzhang
as code owners
timotheeguerin
changed the title
|
You can try these changes at https://cadlplayground.z22.web.core.windows.net/prs/2736/ Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/prs/2736/ |
| import { EmitContext, emitFile, resolvePath } from "@typespec/compiler"; | ||
|
|
||
| export async function $onEmit(context: EmitContext) { | ||
| if (!context.program.compilerOptions.noEmit) { |
There was a problem hiding this comment.
Might it be worth putting something super simple here with the emitter framework, like just printing out model names or some such?
There was a problem hiding this comment.
I wasn't sure I really wanted people to try to use the emitter framework today as there is still a lot of issues with it.
I might take a stab during the holidays at solving all those issues Travis and I got when using it and after I think we could setup the boilperplate for the emitter framework usage.
| } from "@typespec/compiler/testing"; | ||
| import { TestLibrary } from "../src/testing/index.js"; | ||
|
|
||
| export async function createMyTestHost() { |
There was a problem hiding this comment.
I find these names to be a little awkward with "my" in them, could maybe template in the emitter name in place of "my"?
There was a problem hiding this comment.
Yeah that would be great but I think our template engine right now doesn’t have this capability to change casing. I can do a follow up pr that does
Add a new template for scaffolding an emitter
emitter-tstemplate setup the following:Change to the init area
--templatecli option to allow selecting the template without a prompt.Added e2e test for templates
Scafold the template and then run commands like
npm install,npm run build,npm run test, etc. to make sure everything is done correctly.This is quite costly so might be worth separating in a different step