Setup repo to support client generation with tsp-client

[catalinaperalta]

Adding configs necessary to generate client libraries with tsp-client.

Example of how to update emitter-package.json in the future:

PS C:\repos\azure-sdk-for-rust> .\eng\common\scripts\typespec\New-EmitterPackageJson.ps1 -PackageJsonPath <path to>\typespec-rust\packages\typespec-rust\package.json -OutputDirectory .\eng\

There will be a tsp-client specific command coming soon!

To sync the lock file with the emitter-package.json file run: tsp-client generate-lock-file

[heaths]

Can we pass a URL instead of local file path? Currently, we have no plans to colocate the emitter source in this repo. Can we also specify it via config?

[catalinaperalta]

Can we pass a URL instead of local file path? Currently, we have no plans to colocate the emitter source in this repo. Can we also specify it via config?

@hallipr can you help answer this? On the tsp-client side, I can take this into consideration for the new command that will replace the pwsh script.

[hallipr]

Can we pass a URL instead of local file path? Currently, we have no plans to colocate the emitter source in this repo. Can we also specify it via config?

When we use New-EmitterPackageJson for separate emitter and sdk repos, it's typically the emitter repo that calls the script. The sdk repo only contains the emitter-package.json file and has no config or code related to its creation.

Comment addressed

[jhendrixMSFT]

I don't know enough about how this should be structured but the values for the Rust emitter look correct.

[catalinaperalta]

I don't know enough about how this should be structured but the values for the Rust emitter look correct.

This is the final shape. The only action for you is to pin your devDependencies in the typespec-rust emitter to a specific version instead of a range (otherwise you'll have to do it manually in your emitter-package.json updates). In the future you'll follow these steps to update this file with new rust emitter releases:

1. To sync emitter-package.json with the typespec-rust package.json, run:

PS C:\repos\azure-sdk-for-rust> .\eng\common\scripts\typespec\New-EmitterPackageJson.ps1 -PackageJsonPath <path to>\typespec-rust\packages\typespec-rust\package.json -OutputDirectory .\eng\

NOTE: I'll let you know when tsp-client has a command for this so you can stop using the pwsh script

2. To sync your emitter-package-lock.json, run:

tsp-client generate-lock-file

And of course feel free to reach out if you have any questions!