Swashbuckle and schemaId is already used

Swashbuckle can fail to generate a swagger / Open API document with the message "The same schemaId is already used...". This post explains what that means, and offers a way to work around it. "The same schemaId is already used..." When creating a swagger / Open API document with Swashbuckle, it's possible to encounter an error of this nature: Richard Morris explains the reason for this here: > By default, SB uses the short (unqualified name) which has its benefits because it keeps the docs simpler but also it’s downside if model names are duplicated in different namespaces. The solution for this is using the CustomSchemaIds configuration option for Swashbuckle. This allows the customisation of type names, such that collisions are prevented. We need types to be unique strings. A simple way to tackle this is something like this: However, the types created using the above approach can be verbose. Wouldn't it be nice if we could essentially have the names we had before, but just handle duplicates with an incrementing number? Nicer names with SwashbuckleSchemaHelper We can do exactly this. What we'll do is put together a class called SwashbuckleSchemaHelper: The above class borrows the DefaultSchemaIdSelector implementation from Swashbuckle itself. It creates the type name using that, and then uses a Dictionary to track the numbers of usages of it; suffixing a number where there are duplicates to indicate which duplicate is in play on this occasion. This number suffix is inspired by an answer on Stack Overflow and also by Glenn Piper's comment here. Usage of this looks like this: The result of using this approach is that you'll start to generate multiple types: MyType and MyType2, and importantly a goodbye to the "The same schemaId is already used..." message.