Change Details

RESTBase swagger spec has to be made spec-compliant and switched to OpenAPI 3.0. This would require several steps: [x] Replace all the paths that use optional parameters with a set of paths with required parameters, but still be swagger 2.0 compliant. [x] Remove support for optional path parameters from swagger-router and from the spec parser, add support or swagger 3.0 features. 3. Start using swagger 3.0 features.

RESTBase swagger spec has to be made spec-compliant and switched to OpenAPI 3.0. This would require several steps: [x] Replace all the paths that use optional parameters with a set of paths with required parameters, but still be swagger 2.0 compliant. [x] Remove support for optional path parameters from swagger-router and from the spec parser, add support or swagger 3.0 features. [] Replace all the optional paths in the `/sys` hierarchy 3. Start using swagger 3.0 features.

RESTBase swagger spec has to be made spec-compliant and switched to OpenAPI 3.0. This would require several steps: [x] Replace all the paths that use optional parameters with a set of paths with required parameters, but still be swagger 2.0 compliant. [x] Remove support for optional path parameters from swagger-router and from the spec parser, add support or swagger 3.0 features. [] Replace all the optional paths in the `/sys` hierarchy 3. Start using swagger 3.0 features.