Uno.Resizetizer should not be in api doc when a uno app is part of docfx metadata

[DevTKSS]

Current behavior

I included an regular Uno app v5.x in a docfx metadata src but beside my own api, it always also published the Uno.Resizetizer as part of my application api which os not the case at all obviously!

Expected behavior

As every nuget provided api the resizetizer should not get listed as public api of an uno app

How to reproduce it (as minimally and precisely as possible)

Create metadata api from a uno app by using docfx abd only let it use public api of your app as default set , look in the generated metadata

Workaround

Add a exclude with Uno.Resizetizer to the docfx.json

Works on UWP/WinUI

None

Environment

Other, Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia

NuGet package version(s)

No response

Renderer

• Skia
• Native

Affected platforms

Build tasks

IDE

Visual Studio Code, Visual Studio 2022

IDE version

17.3.x

Relevant plugins

No response

Anything else we need to know?

If you know of any changes on resizetizer to 6.0 version I can try it with that version applyed again...

[DevTKSS]

current output produced locally via docfx:

this did include a filter already for build>content>exclude "api/Uno.Resizetizer*.yml" :

because neither my MvuxGallery, nor myself be the Owner or Publisher of the Uno.Resizetizer or any nested Namespace of it, the Resizetizer generated (?) output to process the assets, seems to be set to public accessor, which then causes the symbols to get published as mine.

Althought the docfx settings are or better said "should" exclude the /obj/ folder, it seems like this is not considered by the CLI tool, because as I found the Uno.Resizetizer generated output only in the obj/Debug/* folder:

(the content of the function seems to be conditionally disabled, is this correct also to be this way for Desktop target?)

I would not know, why the Resizetizer generated code should be public accessor so maybe someone could take a look on this?
Will file this as primary on their side issue on docfx repo, hoping this will get fixed somehow. But the problems with generated files and "duplicated files" seem to be already for years a problem, so I have no real hope this will get solved anytime soon.

[DevTKSS]

@jeromelaban is there any specific reason for the generated code (?) of the Resizetizer to have a public accessor and therefore pop up in api doc for a uno ui app like mine?

[DevTKSS]

@ajpinedam for an eventually repro or lookup for you to hopefully help on this issue here maybe:

• docs(XamlNavigation): Update Mvux XamlNavigation Docs with links to the appropriate YouTube tutorials DevTKSS/DevTKSS.Uno.SampleApps#11

There is the problem causing branch linked and you can see the FilterConfig I am using in the attached files of that PR.
The resizetizer content I got excluded with this from the docfx output, but not the mvux products🤔
A possible workaround until those might could be generated as non public accessor would be, if there would be a FilterConfig available that would exclude them🤔