Unexpected operation-level "Servers" block rendered by default in Swagger UI

[leandroluk]

Is your feature request related to a problem? Please describe.

Currently, endpoints in the generated Swagger UI display an operation-level "Servers" dropdown by default (showing /). This overrides global server options, clutters the UI unnecessarily, and is highly uncommon in standard Swagger interfaces.

Describe the solution you'd like

By default, operations should not generate their own servers array unless explicitly configured. They should rely on the global server definition. Please remove the default operation-level server injection or provide an option/flag to disable it globally.

Describe alternatives you've considered

Manually attempting to strip the operation-level servers from the generated OpenAPI schema before serving it to Swagger UI, which is not ideal.

Additional context

Screenshot attached showing the unnecessary block:

[juhaku]

How does the generated openapi.json look like? I highly doubt that the generated openapi.json does not contain the servers definition on operation. The servers will be only parsed per operation if #[path(servers = ...)] attribute is defined.

utoipa/utoipa-gen/src/path.rs

Lines 190 to 197 in b66879a

	"servers" => {
	let servers;
	syn::parenthesized!(servers in input);
	path_attr.servers =
	Punctuated::<Server, Token![,]>::parse_terminated(&servers)?
	.into_iter()
	.collect();
	}

In that case the issue is in the Swagger UI itself.

However, it would be helpful to know what framework integration you are using and what does the openapi.json look like or the utoipa setup in that regard to further investigate the issue.