如何从openapi 2.0生成的对象命名空间中删除破折号

Question

I use Swashbuckle.AspNetCore (v4.0.1) to generate swagger.json file in asp .net core. After the import in Azure API Management we see the following types that we don't expect: SwaggerGenerationSample-Models-EmployeeArray and SwaggerGenerationSample-Models-EmployeeArray-1 etc. .

I expect to have dots instead of dashes SwaggerGenerationSample.Models.EmployeeArray .

I tried to use

CustomSchemaIds(t => t.Name), instead of CustomSchemaIds(t => t.FullName)

but don't work due to some duplicated object names (Request.Employee and Response.Employee).

I currently have the following configuration in AspNetCore.

services.AddSwaggerGen(config => {
   config.DescribeAllEnumsAsStrings();
   config.CustomSchemaIds(type => type.FullName);
   config.SwaggerDoc("v1", new Info { Title = "SampleAPI", Version = "v1" });
   config.MapType<decimal>(() => new Schema { Type = "number", Format = "double" });
   config.MapType<decimal?>(() => new Schema { Type = "number", Format = "double" });
 });

Answer 1

I believe , this is because of the recent changes how Open API import and export works in APIM. You can find the semantics here as it aligns with it.

Here is the normalization rule for the same:

Normalization rules for operationId

• Convert to lower case.
• Replace each sequence of non-alphanumeric characters with a single dash, eg GET-/foo/{bar}?buzz={1} will be transformed into get-foo-bar-buzz-1- .
• Trim dashes on both sides, eg get-foo-bar- will become get-foo-bar
• Truncate to fit 76 characters, four characters less than maximum limit for a resource name.
• Use remaining four characters for a deduplication suffix, if necessary, in the form of -1, -2, …, -999.

You can read more about it here :

https://blogs.msdn.microsoft.com/apimanagement/2018/04/11/important-changes-to-openapi-import-and-export/

Hope it helps.