Support new UseInlineDefinitionsForObjects flag

[sol-wasserman]

Problem

When a request/response has a nested object, there are two pieces of information missing from the generated doc file:

1. The property's summary is not displayed.
2. The Nullable marker is not shown for nullable properties.

---

Here's a screenshot of what it looks like now:

Here's a screenshot of the source code for the above:

As you can see, this property has a nice summary, and is nullable.

Here's a screenshot of what it I would expect:

Underlying Cause

It looks to me like the reason it's not generating that properly is because the object is only a reference, and Swagger doesn't support these on references. As the Swagger specification says, regarding $refs:

This object cannot be extended with additional properties and any properties added SHALL be ignored.

Proposed Solution

We have previously introduced an option to UseInlineDefinitionsForEnums. Among other things, this will show the summary of a property that is an enum, and will also show the Nullable marker accordingly.

This PR adds a similar UseInlineDefinitionsForObjects option. When enabled, it'll inline the whole schema, and will properly show the summary and whether it's nullable:

[sol-wasserman]

@domaindrivendev Just checking in whether you got a chance to look at this.

Is there a better approach to achieving this? Or is there anything else I can improve in this PR?

Thanks in advance.

[xinge-shizhiqiang]

我也遇到了这个问题 这个问题解决了吗

[sol-wasserman]

This issue was accidentally closed. I've reopened it here: #2533.

[xinge-shizhiqiang]

升级到最新的6.5.0版本后 使用了UseAllOfToExtendReferenceSchemas()而不是UseInlineDefinitionsForObjects()问题解决了 谢谢老兄！

…

------------------ 原始邮件 ------------------ 发件人: "Sol ***@***.***>; 发送时间: 2022年12月21日(星期三) 凌晨0:42 收件人: ***@***.***>; 抄送: ***@***.***>; ***@***.***>; 主题: Re: [domaindrivendev/Swashbuckle.AspNetCore] Support new `UseInlineDefinitionsForObjects` flag (PR #2384) This issue was accidentally closed. I've reopened it here: #2533. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>