Releases: chgeo/cds-swagger-ui-express
Releases · chgeo/cds-swagger-ui-express
v0.10.0
Added
- The OpenAPI spec is no available for download on
.../openapi.json
and linked in the UI.
Changed
- The default value for option
apiPath
is now/
, allowing more flexible control over the root path where the CDS services are served. Formerly, it was not possible to set root path relative to the current host, likeabc.com/1234-appid/$api-docs/...
,abc.com/5678-appid/$api-docs/...
.
v0.9.0
Changed
- Use
@cap-js/openapi
instead of@sap/cds-dk
, leading to lighter dependencies
v0.8.0
Added
- Auto-registration mode: the middleware registers itself when loaded as a CAP plugin
- Declarative configuration through
package.json
/cds-rc.json
- Programmatic registration is still possible, but disables auto mode then
Changed
- Make dependency to
@sap/cds-dk
optional. If running with thecds
executable during development, the dependency is fulfilled anyways. Only when running as part of a deployed app withcds-serve
, then such a dependency is needed.
v0.7.0
Changed
- Requires
@sap/cds
^7 - Requires
@sap/cds-dk
^7 - Requires
swagger-ui-express
/swagger-ui
^5 - Drops Node 14 and 16 support. Minimum Node version is now 18.
Added
- New option
odataVersion
to specify the OData version used to compile the OpenAPI specs
Fixed
- Works with
@sap/cds
7.4 again
v0.6.0
Version 0.6.0 - 2023-02-27
Added
- Way to pass swagger (UI) options. See README.md.
- JSDoc type definitions for options.
Changed
- The default site title is now <Service Name> - Swagger UI (instead of just Swagger UI)
- REST services are now available as well in the Swagger UI. Previously, only OData services were allowed. This was to avoid potential issues as the underlying OpenAPI transformation uses OData as intermediate protocol. So, as long as we don't see issues, allow REST services as well.
Fixed
- Multiple services are now properly served, w/o the previous stale content of
swagger-ui-init.js
. Requiresswagger-ui-express
>= 4.6.2