4763126d3f | ||
---|---|---|
.. | ||
_build | ||
images | ||
template/styles | ||
README.md | ||
docfx.json | ||
favicon.ico | ||
index.md | ||
toc.yml |
README.md
Build API documentation
The API documentation is generated by using DocFX.
The last version of the API documentation is in the apiguide/
folder of gh-pages
branch. If you want to create a new version of the API documentation:
-
Commit your changes before start the build process.
-
Run the powershell script
docs/_build/makeApiDocs.ps1
.makeApiDocs.ps1
script should create the folderapiguide-tmp/
with the API documentation.makeApiDocs.ps1
script should:- copy a part of repository to the temporary folder
InferNet_Copy_Temp
, - build
PrepareSource.csproj
project, - run
PrepareSource.exe
for theInferNet_Copy_Temp
folder, - install NuGet package
docfx.console
, - run
docfx
, - remove temporary folder
InferNet_Copy_Temp
, - switch to
gh-pages
, - create commit with the new changes.
- copy a part of repository to the temporary folder
-
Push new changes to the
gh-pages
.
Documenting Factors
Infer.NET
provides tool to automatically generate description text for factor classes, i.e. classes marked with [FactorMethod]
attribute. Generated descriptions are written to src/Runtime/Factors/FactorDocs.xml
file and referenced using <include>
tags in source code triple comments.
It is important to have full and correct description of all factors, so when you change existing factor or add new one, please follow steps below.
-
Add triple comment
/// <include file='FactorDocs.xml' path='factor_docs/message_op_class[@name="FactorClassName"]/doc/*'/>
before newly created factor classes. Replace
FactorClassName
with actual class name without namespace. -
Run
BuildFactorDoc
project from Microsoft Visual Studio or .NET Core CLI. -
Commit updated
src/Runtime/Factors/FactorDocs.xml
.