Should we ban use of tspconfig imports
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 90
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 156
Description
Example specification/ai-foundry/data-plane/Foundry/src/sdk-service-agents-contracts/tspconfig.yaml
Doesn't feel like there is any value over import in the typespec itself just add confusion on where things are coming from
```yaml
imports:
- "@azure-tools/typespec-azure-core"
- "@azure-tools/typespec-azure-core/experimental"
- "@azure-tools/typespec-client-generator-core"
# Note: Imports for OpenAI types may use alternate views per tspconfig.yaml
- "@azure-tools/openai-typespec/views/client-emitters/models/evals"
- "@azure-tools/openai-typespec/views/client-emitters/models/fine-tuning"
- "@azure-tools/openai-typespec/views/client-emitters/models/responses"
```
Contributor guide
Research direction
Start by reading specification/ai-foundry/data-plane/Foundry/src/sdk-service-agents-contracts/tspconfig.yaml and compare its imports with imports declared in the corresponding TypeSpec files. Determine whether the tspconfig imports are redundant or serve alternate views, then document a decided convention and update affected configurations if a ban is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100