Java Deprecated annotation issue
Mattias-Sehlstedt has helpfully created a PR that fixes my issue: https://github.com/swagger-api/swagger-core/pull/5099. This issue is causing a significant issues in my development work. Are these forums the correct place to attempt to bring visibility to this issue? I very much do not want the work in that PR to go to waste, and I would like to get the issue fixed. What happens is that when I annotate a field in one class with @Deprecated, then every other field with the same name also becomes deprecated, and my openapi spec is not correct. For example I just needed to deprecate a `name` field, and now every single `name` field is marked deprecated: @@ -19023,6 +19038,7 @@ "type": "string" }, "name": { + "deprecated": true, "type": "string" }, "rate": { @@ -22081,6 +22097,7 @@ "type": "string" }, "name": { + "deprecated": true, "type": "string" } }, @@ -23678,6 +23695,7 @@ "type": "string" }, "name": { + "deprecated": true, "type": "string" },
OpenApi Spec for AWS ApiGateway doesn't allow 1 attribute to read its value dynamically
We opened a Ticket for AWS but they mention its related to OpenApi Spec so adding details here of that ticket: We follow doc and found issue Under "x-amazon-apigateway-integration" doc mentions "integration-target" or "integrationTarget" If we replace integrationTarget from hardcoded ALB Arn and try to use dynamic ex using Stage Variable like ${stageVariables.ALB_ARN} : Terraform Plan shows: resource "aws_api_gateway_rest_api" "rest_api" { ~ body = jsonencode( ~ { ~ paths = { ~ "/prx/version" = { ~ get = { ~ x-amazon-apigateway-integration = { ~ integrationTarget = "arn:aws:elasticloadbalancing:eu-west-1:590184133945:loadbalancer/app/legacy-service-priv-dev/69014ccf971cb582" -> "${stageVariables.legacyServiceAlbArn}" Terrafom Apply gives error: module.api_gateway_all_private.aws_api_gateway_rest_api.rest_api: Modifying... [id=889jk5o63f] ╷ │ Error: updating API Gateway REST API (889jk5o63f) specification: operation error API Gateway: PutRestApi, https response error StatusCode: 400, RequestID: 9ebcf1c5-688e-4b19-8935-40d436904592, BadRequestException: Errors found during import: │ Unable to put integration on 'GET' for resource at path '/prx/version': ${stageVariables.legacyServiceAlbArn} is not a valid ALB or NLB arn So basically open api spec doesn't support integrationTarget to read dynamically which is a issue, where as uri & connectionId are allowed to read value dynamically.
Regarding swagger is not working in nodejs as per the swagger document.
Hi there, I tried to setup swagger on nodejs as per the document par it is not working and present wrong data of swagger UI see the below attached screenshot. So just wanted to know how to setup swagger in nodejs so that all my apis display in one place. I tried lot of solutions on different different websites but same issue appeared. So kindly guide how to do that so that swagger is running properly. Reference site that I tried below: https://swagger.io/docs/open-source-tools/swagger-codegen/#:~:text=The%20Swagger%20Codegen%20is%20an,can%20be%20found%20in%20GitHub. https://levelup.gitconnected.com/how-to-add-swagger-ui-to-existing-node-js-and-express-js-project-2c8bad9364ce https://medium.com/bb-tutorials-and-thoughts/how-to-add-swagger-to-nodejs-rest-api-7a542cfdc5e1 https://plainenglish.io/blog/how-to-implement-and-use-swagger-in-nodejs-d0b95e765245 https://dev.to/kabartolo/how-to-document-an-express-api-with-swagger-ui-and-jsdoc-50do https://itnext.io/setting-up-swagger-in-a-node-js-application-d3c4d7aa56d4 https://github.com/Surnet/swagger-jsdoc/blob/master/README.md Looking forward to hearing from you. Thanks! Swagger.json: { "swagger": "2.0", "info": { "version": "1.0.0", "title": "My User Project CRUD", "description": "My User Project Application API", "license": { "name": "MIT", "url": "https://opensource.org/licenses/MIT" } }, "host": "localhost:3000", "basePath": "/", "tags": [ { "name": "Users", "description": "API for users in the system" } ], "schemes": ["http"], "consumes": ["application/json"], "produces": ["application/json"] } Server.js: import swaggerUi from 'swagger-ui-express'; import swaggerDocument from './swagger.json'; app.use( '/api-docs', swaggerUi.serve, swaggerUi.setup(swaggerDocument) ); app.listen(port, () => { console.log(`Server running at ${process.env.SERVER_URL}`); });
How to Integrate Swagger for jenkins REST API Documentation
Hello everyone, I'm a prospective GSoC participant with Jenkins and I'm exploring a project idea that involves integrating Swagger/OpenAPI for documenting the Jenkins REST API. Could anyone share insights on whether a full integration is feasible during GSoC, what potential challenges might arise, and any resources or documentation that might help? Project idea details: https://www.jenkins.io/projects/gsoc/2025/project-ideas/swagger-openapi-for-jenkins-rest-api/ Anyone's suggestion or guidance will means a lot to me, Thanks in advance for your guidance !!!
Avoid caching AnnotationIntrospector to support custom module loading. Issue: #4744
https://github.com/swagger-api/swagger-core/blob/24fca016b28d3f8363b29471312d3678a0f7a542/modules/swagger-core/src/main/java/io/swagger/v3/core/jackson/AbstractModelConverter.java#L46 Issue: Currently, binding the annotation introspector to _intr in `AbstractModelConverter.java` causes a divergence in functionality between Swagger's annotation introspector and Jackson's annotation introspector. This could lead to inconsistencies, especially when users extend Jackson with custom modules that perform custom annotation introspection. Solution: To address this, I propose that we avoid binding the introspector directly and instead retrieve the current annotation introspector from _mapper. This approach ensures that both Swagger and Jackson utilize the same introspector, maintaining functionality and consistency across the system. Use Case: This change is particularly beneficial for users implementing custom annotation introspection Github Issue Link: https://github.com/swagger-api/swagger-core/issues/4744 Github PR Link: https://github.com/swagger-api/swagger-core/pull/4728 Note: I hope this is the right forum to bring attention to the Github Issue and PR I created. I tried tagging maintainers in the PR, but failed to bring attention.
Swagger 2.0 to OpenApi 3.0
we are using all the classes with import io.swagger.annotations.*; and we have moved to jakarta. Please let me know where I can find the documentation to know what are annotations to be used. Please also suggest me swagger maven plugin which takes jakarta into consideration and generate a JSON file. Attach sample plugin to be used to generate JSON with open api 3 or greater.
