Feature: tspconfig project with entrypoint

[timotheeguerin]

No description provided.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/compiler@10548

commit: 6353917

[github-actions]

All changed packages have been documented.

• ✅ @typespec/compiler

Show changes

@typespec/compiler - feature ✏️

Add kind: project and entrypoint support to tspconfig.yaml for defining project boundaries and entrypoint resolution. See Project Configuration for more details.,> ,> yaml title=tspconfig.yaml,> kind: project,> entrypoint: src/service.tsp,> emit:,> - "@typespec/openapi3",>

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension

[markcowl]

Does this mean we should eventually change the structure of azure-rest-api-specs typespec projects?

The behavior here is that, if there is a project tspconfig.yaml in the path ancestors of the command line path, the config entrypoint will always be used. I think this either means that all azure-rest-api-specs configs should not use project configs, or that we need another project config for client customizations in another directory, and TypeSpecValidation will have to be changed accordingly.

Am I getting the behavior wrong, or is this the intention?