I had a great opportunity to use the (new in Swift 5.8) capability for changing the permissions level for documentation symbols, and it works beautifully. I ended up having to bound it to preserve backwards compatibility, so it makes a bit of bigger wart than you'd hope for in an annotation, but it does the trick:
The only downside is now that we can hide some, I'm getting requests to hide more. In particular, some of the compiler generated conformance methods - hash(into:), !=(:), and init(from:) being the common culprits.
Are there any options to handle this scenario where I can't annotate those methods to "obscure them" from a documentation generation perspective?
These are what the compiler calls "synthesized symbols", and they can be hidden by passing an extra flag when getting symbol graphs: -skip-synthesized-members. This will drop all the symbols that came in from protocol extensions, which should get you most of the way there.
Is that exposed up through swift-docc-plugin, or would I need to step down into separately generating the symbols (using this option) in order to use this? I didn't see it as an option within swift package plugin generate-documentation --help
Did you ever find an answer for this? These excessive protocol implementation documentation artifacts make the document index unusable in my instance. There are hundreds of them listed for me and we are using DocC for a project, not just a package.
If we could plug in the -skip-synthesized-members flag somewhere, that would be ideal.