[Bug]: ALDoc missing information about extended objects

[navdotnetreqs]

AL-Go version

6.3

Describe the issue

I noticed that the ALDoc-build is missing information about the extended objects:

To fix this, it is actually enough to add the -c $packagesFolder parameter to the aldoc build command in
\BuildReferenceDocumentation\BuildReferenceDocumentation.HelperFunctions.ps1
where $packagesFolder is .alpackages or wherever Microsoft's app-files are found.

However, the dependency app-files don't seem to be present for the documentation workflow run.

Expected behavior

References generated correctly.

Steps to reproduce

Run the document generation. Example images are made using pdf build, example code in
#1448

Additional context (logs, screenshots, etc.)

I noticed that the ALDoc-build is missing information about the extended objects:

To fix this, it is actually enough to add the -c $packagesFolder parameter to the aldoc build command in
\BuildReferenceDocumentation\BuildReferenceDocumentation.HelperFunctions.ps1
where $packagesFolder is .alpackages or wherever Microsoft's app-files are found.

However, the dependency app-files don't seem to be present for the documentation workflow run.

[freddydk]

Yeah, this is a bug
The problem is really (as you say) that dependencies and Microsoft apps are not downloaded.

We will have a look at this

[navdotnetreqs]

Works in local development now ( #7965 ) so it likely works in AL-Go as well (haven't tested yet).