Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resources grouping ignoring tags with common path name and different resources #675

Open
a819694114 opened this issue Feb 28, 2024 · 4 comments
Assignees
Labels
area:server This item is related to the server extension enhancement New feature or request

Comments

@a819694114
Copy link

I have one single .json file used to generate server code.
I have some paths looks like this:
/some/path/first
/some/path/second
Right now I see that I will have one file generated called SomeResource.java
I wonder if I can have two files: FirstResource.java and SecondResource.java
When I use the client generation, I would get two API files: FirstApi.java and SecondApi.java with tags. This seems to be missing in the server generation.

Here is the detailed sample file I have:

{
  "openapi": "3.0.2",
  "info": {
    "title": "API Title",
    "version": "1.0"
  },
    "servers": [
       {
          "url": "https://api.test.com",
          "description": "Server"
       }
    ],
  "paths": {
      "/some/path/first": {
         "put": {
            "tags": [
               "First"
            ],
            "parameters": [
               {
                  "name": "Accept",
                  "in": "header",
                  "schema": {
                     "type": "string"
                  },
                  "example": "application/json"
               }
            ],
            "responses": {
               "200": {
                  "description": "success"
               }
            }
         }
      },
      "/some/path/second": {
         "put": {
            "tags": [
               "Second"
            ],
            "parameters": [
               {
                  "name": "Accept",
                  "in": "header",
                  "schema": {
                     "type": "string"
                  },
                  "example": "application/json"
               }
            ],
            "responses": {
               "200": {
                  "description": "success"
               }
            }
         }
      }
  }
}
@hbelmiro hbelmiro added the area:server This item is related to the server extension label Feb 29, 2024
@carlesarnal carlesarnal added the enhancement New feature or request label Mar 12, 2024
Copy link
Contributor

@ricardozanini @hbelmiro This is being labeled as Stale.

Copy link
Contributor

@ricardozanini @hbelmiro This is being labeled as Stale.

@github-actions github-actions bot added the Stale label Jul 13, 2024
Copy link
Contributor

@ricardozanini @hbelmiro This is being closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 20, 2024
@carlesarnal carlesarnal reopened this Sep 23, 2024
@github-actions github-actions bot removed the Stale label Sep 23, 2024
Copy link
Contributor

@ricardozanini @hbelmiro This is being labeled as Stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:server This item is related to the server extension enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants