How to set the 'api-version' option for multi-service package in tspconfig.yaml

[JialinHuang803]

Currently tspconfig.yaml allows an api-version option as a string, which is also used in multi-service scenarios and leads to problems in the generated code. Should we enable setting multiple api-versions here, or should we disable this field when dealing with multiple services?

If we decide to support this option for multiple services, does it function the same way as useDependency in client.tsp?

[lmazuel]

That's an interesting question. The point of setting api-version is to be able to generate a SDK that shouldn't point to the latest API version. I would assume it's possible we may want to ship a Compute SDK where all services are not necessarly projected to the latest api-version. That would require a mapping service->api-version in the tsp-config then. api-version in tsp-config is rare, and multi-service is rare, so do we think we would need that feature?

[JialinHuang803]

As we discussed offline, let's wait on implementing this feature until we encounter actual cases.