Generate servers description about createapi HOT 3 CLOSED

I think it can automatically generate a (rather useless) name but then the user can create a mapping based on the host (not including port for YAML purposes),

servers:
  - https://production.com:Production
  - http://staging.dev:Staging

Edit: well, I guess port removal would actually be problematic in case they separate based on ports. Also if the URLs differ by subdirectories, so full URL mapping would be needed.

Edit to the edit: didn't know about templating for URLs, seems like this would be an extensive feature.

from createapi.

Right, maybe it's best to leave it out of the scope, just like authentication. I don't see how you can possibly generate anything useful without having a basic name field.

from createapi.

I think this would be possible with just a full mapping of the URL, template and all.

servers:
  - production: "https://production.com"
  - developing: "https://{customerId}.developing.com"

OpenAPIKit gives us an extensive URLTemplate object which we can probably create an enum for each server and the variables are filled in as the associated values:

enum Servers {
	case production
	case developing(customerId: String)
	
	var url: URL? {
		...
		case .developing(let customerId):
			// replace the variables in a URLTemplate and use their built in `.url` construction
			// or whatever we put here
	}
}

The ParallelDocumentParser just needs the decoding:

var servers: Result<[OpenAPI.Server], Error>!
perform(in: group) {
    servers = Result(catching: { try container.decode([OpenAPI.Server].self, forKey: .servers) })
}

While there is no name feature which would be the best thing, we can just have the default be alphabetical. This default doesn't seem like an issue for me as users that would use this feature would manually create the mapping anyways to work with it.

from createapi.