Open MarcusFelling opened 3 years ago
It would be really nice to support this in an easy-to-use manner.
For now, here's a manual way to get this working using the current infrastructure:
--specs-dir
parameter to the path you have cloned the specs repo to, and using the --single-path
option where the path specified is the relative path to the README.md
you're trying to generate types for. E.g. for the compute readme at specification/compute/resource-manager/readme.md
, this value would simply be compute
.ProjectReference
instead of PackageReference
, replacing {path_to_bicep_types_repo}
with the path where you cloned this repo: https://github.com/Azure/bicep/blob/ec0c24b90d4358020131ab9b9faa234bf5502359/src/Bicep.Core/Bicep.Core.csproj#L28-L29.
<ProjectReference Include="{path_to_bicep_types_repo}/src/Bicep.Types/Bicep.Types.csproj" />
<ProjectReference Include="{path_to_bicep_types_repo}/src/Bicep.Types.Az/Bicep.Types.Az.csproj" />
I would love the ability to consume resource types that are in private preview. This would help test this experience before types move to public preview.