Open GarfieldJiang opened 1 month ago
What's happens when using following regex?
- exclude:
uidRegex: ^Global\.
type: Type
It seems when excluding global namespace. All types are excluded from metadata generations.
I'll give it a try tomorrow!
What's happens when using following regex?
- exclude: uidRegex: ^Global\. type: Type
It seems when excluding global namespace. All types are excluded from metadata generations.
It works with a little glitch. When clicking the 'API' link on the home page, I go to the api/toc.yml page, which is correct. However, the addr localhost:8080/api leads me to a stylesheet like page, listing all the htmls in the generated api folder.
However, the addr localhost:8080/api leads me to a stylesheet like page, listing all the htmls in the generated api folder.
It thought these pages are generated by ASP.NET DefaultFilesMiddleware
.
This middleware will provide a default index page if the index.html
file does not exist in the specified directory.
So it's not relevant to the filterconfig settings.
There is an existing [Feature Request]
issue to generate index.html
file on docfx build phase (#2865)
But it's not implemented yet.
However, the addr localhost:8080/api leads me to a stylesheet like page, listing all the htmls in the generated api folder.
It thought these pages are generated by ASP.NET
DefaultFilesMiddleware
.This middleware will provide a default index page if the
index.html
file does not exist in the specified directory. So it's not relevant to the filterconfig settings.There is an existing
[Feature Request]
issue to generateindex.html
file on docfx build phase (#2865) But it's not implemented yet.
Thanks for the explanation.
Describe the bug
I'm using Unity and making common libraries. I hope to generate docs using the C# source code, cuz current dotnet version won't well restore Unity csprojs. (
dotnet restore
will outputNothing to do
or something alike, and docFX will freeze there, but this is not a problem to me).I use filterConfig.yml and exclude
Global
namespace in it (I have"globalNamespaceId": "Global"
in docfx.json), but this prevents the metadata to generate the destination dir.The content of my filterConfig.yml
Things work quite well if I don't have this exclude part.
To Reproduce Steps to reproduce the behavior:
MyNamespace
namespace.docFX docfx.json --serve
or things alike.Expected behavior The destination folder (
api
) should exist but doesn't.Context (please complete the following information):
OS: MacOS 14.4.1 + intel chips
Docfx version: 2.76.0
.NET version: 8.0.301 (output by dotnet --version)
docfx.json
configAdditional context Add any other context about the problem here.