Skip to content

[FEATURE REQ] Support TypeSpec code generation for v2 libraries in CI #46214

@vcolin7

Description

@vcolin7

Is your feature request related to a problem? Please describe.

Currently, we don't support generating v2 libraries in CI because of 2 things:

  • The latest publicly available version of TypeSpec does not support the azurev2 flavor
  • TSP configuration between v1 and v2 libraries is different from one another and we don't currently have a way to tell the code generator to pick a specific file (it defaults to client.tsp).

Describe the solution you'd like
A way to tell the TypeSpec code generator which file to use for client generation once v2 is publicly supported.

Describe alternatives you've considered
Skipping code generation in CI.

Additional context
N/A

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

  • Description Added
  • Expected solution specified

Metadata

Metadata

Assignees

Labels

Azure.Core.V2Contains issues to consider when desiging Azure Core V2ClientThis issue points to a problem in the data-plane of the library.KeyVaultclientcore

Projects

Status

Untriaged

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions