Resources grouping ignoring tags with common path name and different resources

[a819694114]

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"
               }
            }
         }
      }
  }
}

[github-actions]

@ricardozanini @hbelmiro This is being labeled as Stale.

[github-actions]

@ricardozanini @hbelmiro This is being labeled as Stale.

[github-actions]

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