Polyglot API docs

[sebastienros]

In some integrations we have [AspireExportIgnore] with a Reason and sometimes there is a <remarks> on the method stating the method is not available in polyglot.

Could we use this property in the API docs generated site, and [AspireExport] to document the polyglot aspect? At minimum for now by adding a tag/note that the method is not available in Polyglot app hosts, then we could remove these remarks. And ideally also be able to expose the signature of the method in the target language (tabs?) but that would be more work for later.

[IEvangelist]

In some integrations we have [AspireExportIgnore] with a Reason and sometimes there is a on the method stating the method is not available in polyglot.

This doesn't make sense to me. Are you saying you want us to document when something isn't emitted? I think it makes more sense to instead, only generate docs for what is actually generated for the polyglot.

What UX would you expect to display, what value would a consumer get out of such details? Happy to discuss, just not sure I see what you're getting at.