Open rmannibucau opened 1 month ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 78.86%. Comparing base (
fe673ec
) to head (f89ff73
). Report is 191 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
BuildJsonConfig
has Output
property that can be used to change output directory
by setting this property.
Is there any missing features that can not be covered above solution?
Note:
There is following behavior differences. So it might need to explicitly set full path
.
BuildJsonConfig
's Output
property. relative path is resolved based on docfx.json
config path.outputDirectory
parameter. It's resolved based on current directory.Hi
One issue is the configuration is internal so programmatically it would require to generate a json file, I'd prefer something closer to docfx project api if possible.
One issue is the configuration is internal
I've forgotten that BuildJsonConfig
can't access programmatically because it's declared as internal
.
I've requested to change these options to public
before at #8872.
But currently there is no progress.
As a temporary workaround.
By using IgnoresAccessChecksToGenerator
.
It can use RunBuild.Exec
method directly instead of Docset.Build
API.
Example configs of csproj
<ItemGroup>
<PackageReference Include="IgnoresAccessChecksToGenerator" Version="0.7.0" PrivateAssets="All" />
<InternalsAssemblyName Include="Docfx.App" />
<InternalsAssemblyName Include="Docfx.Dotnet" />
</ItemGroup>
@filzrev it would work but does it make sense to not expose what doxfx project uses or should docfx not use this output param anymore then?
guess we can drop this PR is https://github.com/dotnet/docfx/pull/10010 will reach main repo anytime soon, wdyt?
@dotnet-policy-service agree