Skip to content

Conversation

@MikeEdgar
Copy link
Contributor

Currently, when the OpenAPI OperationFilter is not used (by disabling several configuration properties to auto-add API information), the scanner will still set x-quarkus-openapi-method-ref extensions in the model for each API operation. This change prevents adding the method-refs when the OperationFilter is not part of the build process.

@quarkus-bot
Copy link

quarkus-bot bot commented Nov 28, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 25432f0.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.


Flaky tests - Develocity

⚙️ JVM Tests - JDK 21

📦 extensions/smallrye-openapi/deployment

io.quarkus.smallrye.openapi.test.jaxrs.OpenApiDefaultPathTestCase.testOpenApiPathAccessResource - History

  • 1 expectation failed. Expected header "Content-Type" was not "application/yaml;charset=UTF-8", was "application/json; charset=utf-8". Headers are: content-type=application/json; charset=utf-8 content-length=3055 - java.lang.AssertionError
java.lang.AssertionError: 
1 expectation failed.
Expected header "Content-Type" was not "application/yaml;charset=UTF-8", was "application/json; charset=utf-8". Headers are:
content-type=application/json; charset=utf-8
content-length=3055

	at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
	at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)

@MikeEdgar
Copy link
Contributor Author

Another victim of #50563

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant