-
Notifications
You must be signed in to change notification settings - Fork 1.1k
feat: openapi spec contributor extension point #4258
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,153 @@ | ||
| --- | ||
| lang: en | ||
| title: 'Extending OpenAPI Specification' | ||
| keywords: LoopBack 4.0, LoopBack 4 | ||
| sidebar: lb4_sidebar | ||
| permalink: /doc/en/lb4/Extending-OpenAPI-specification.html | ||
| --- | ||
|
|
||
| ## OpenAPI Specification Enhancer | ||
|
|
||
| The APIs in a LoopBack `RestApplication` are described by the | ||
| [OpenAPI Specification (short for OAS)](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md). | ||
| An application's OAS is mainly generated from | ||
| [controllers](https://loopback.io/doc/en/lb4/Controllers.html) and their | ||
| members' metadata. Besides this, we would also like to contribute specifications | ||
| from other places. Therefore, an extension point `OASEnhancerService` is created | ||
| to allow registered extensions to provide their OAS fragments and modify a rest | ||
| application's specification. | ||
|
|
||
| _Read about the extension point/extension pattern in | ||
| [documentation](Extension-point-and-extensions.md)_ | ||
|
|
||
| ## Adding a New OAS Enhancer | ||
|
|
||
| Interface `OASEnhancer` is created in `@loopback/openapi-v3` to describe the | ||
| specification enhancers. A typical OAS enhancer class should have a string type | ||
| `name` field and a function `modifySpec()` to modify the current specification. | ||
|
|
||
| For example, to modify the `info` field of an OAS, you can create an | ||
| `InfoSpecEnhancer` that implements interface `OASEnhancer` as follows: | ||
|
|
||
| ```ts | ||
| import {bind} from '@loopback/core'; | ||
| import { | ||
| mergeOpenAPISpec, | ||
| asSpecEnhancer, | ||
| OASEnhancer, | ||
| OpenApiSpec, | ||
| } from '@loopback/openapi-v3'; | ||
|
|
||
| /** | ||
| * A spec enhancer to add OpenAPI info spec | ||
| */ | ||
| @bind(asSpecEnhancer) | ||
| export class InfoSpecEnhancer implements OASEnhancer { | ||
| // give your enhancer a proper name | ||
| name = 'info'; | ||
|
|
||
| // takes in the current spec, modifies it, and returns a new one | ||
| modifySpec(spec: OpenApiSpec): OpenApiSpec { | ||
| const InfoPatchSpec = { | ||
| info: {title: 'LoopBack Test Application', version: '1.0.1'}, | ||
| }; | ||
| // the example calls a default helper function to merge the fragment spec. | ||
| const mergedSpec = mergeOpenAPISpec(spec, InfoPatchSpec); | ||
| return mergedSpec; | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| - The class is decorated with a binding template `asSpecEnhancer`. | ||
| - The enhancer has a name as `info`. Name can be used to retrieve a certain | ||
| enhancer (explained in the | ||
| [extension point section](#oas-enhancer-service-as-extension-point)). | ||
| - The enhancer changes the current specification's `info` object in function | ||
| `modifySpec`. | ||
| - It calls [`mergeOpenAPISpec`](#default-merge-function) to merge the | ||
| specification fragment into the current spec. | ||
|
|
||
| ### Default Merge Function | ||
|
|
||
| Since `modifySpec` has full access to the current spec, it can perform any | ||
| operation: merge, delete, or more complicated changes. This is totally | ||
| determined by the extension contributor. | ||
|
|
||
| To apply the basic merging, we provide a default helper function called | ||
| `mergeOpenAPISpec` that leverages | ||
| [`json-merge-patch`](https://github.com/pierreinglebert/json-merge-patch) to | ||
| merge two json objects. You can find its usage in the | ||
| [previous section](#adding-a-new-oas-enhancer) | ||
|
|
||
| ### Registering an Enhancer | ||
|
|
||
| After decorating your enhancer properly with `@bind(asSpecEnhancer)`, you can | ||
| bind it to your application as follows: | ||
|
|
||
| ```ts | ||
| import {createBindingFromClass} from '@loopback/core'; | ||
| import {InfoSpecEnhancer} from './enhancers/infoSpecEnhancer'; | ||
|
|
||
| class MyApplication extends RestApplication { | ||
| constructor() { | ||
| super(); | ||
| this.add(createBindingFromClass(InfoSpecEnhancer)); | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ## OAS Enhancer Service as Extension Point | ||
|
|
||
| The OAS enhancer extension point is created in package `@loopback/openapi-v3`. | ||
| It organizes the registered OAS enhancers, and provides APIs to either apply one | ||
| enhancer by name, or apply all enhancers automatically. | ||
|
|
||
| ### Registering an Enhancer Service | ||
|
|
||
| You can bind the OAS enhancer extension point to your app via key | ||
| `OAS_ENHANCER_SERVICE`: | ||
|
|
||
| ```ts | ||
| import {RestApplication} from '@loopback/rest'; | ||
| import {OASEnhancerService, OAS_ENHANCER_SERVICE} from '@loopback/openapi-v3'; | ||
|
|
||
| class MyApplication extends RestApplication { | ||
| constructor() { | ||
| super(); | ||
| this.add( | ||
| createBindingFromClass(OASEnhancerService, { | ||
| key: OAS_ENHANCER_SERVICE, | ||
| }), | ||
| ); | ||
| } | ||
|
|
||
| // define a function to return a spec service by the same key | ||
| getSpecService() { | ||
| return this.get(OAS_ENHANCER_SERVICE); | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ### Applying Registered Enhancers | ||
|
|
||
| To automatically apply all the registered enhancers, call `applyAllEnhancers`: | ||
|
|
||
| ```ts | ||
| await app.getSpecService.applyAllEnhancers(); | ||
| ``` | ||
|
|
||
| _In the future we will support applying enhancers by a custom sequence. The | ||
| sequence will be determined by a combination of group names and the alphabetical | ||
| order._ | ||
|
|
||
| To retrieve an enhancer by name, call `getEnhancerByName`: | ||
|
|
||
| ```ts | ||
| await app.getSpecService.getEnhancerByName('info'); | ||
| ``` | ||
|
|
||
| To apply an enhancer by name, call `applyEnhancerByName`: | ||
|
|
||
| ```ts | ||
| await app.getSpecService.applyEnhancerByName('info'); | ||
| ``` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
28 changes: 28 additions & 0 deletions
28
packages/openapi-v3/src/__tests__/unit/enhancers/fixtures/application.ts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| // Copyright IBM Corp. 2019. All Rights Reserved. | ||
| // Node module: @loopback/openapi-v3 | ||
| // This file is licensed under the MIT License. | ||
| // License text available at https://opensource.org/licenses/MIT | ||
|
|
||
| import {Application, createBindingFromClass} from '@loopback/core'; | ||
| import {OASEnhancerService, OAS_ENHANCER_SERVICE} from '../../../..'; | ||
| import {InfoSpecEnhancer} from './info.spec.extension'; | ||
| import {SecuritySpecEnhancer} from './security.spec.extension'; | ||
|
|
||
| export class SpecServiceApplication extends Application { | ||
| constructor() { | ||
| super(); | ||
| this.add( | ||
| createBindingFromClass(OASEnhancerService, { | ||
| key: OAS_ENHANCER_SERVICE, | ||
| }), | ||
| ); | ||
| this.add(createBindingFromClass(SecuritySpecEnhancer)); | ||
| this.add(createBindingFromClass(InfoSpecEnhancer)); | ||
| } | ||
|
|
||
| async main() {} | ||
|
|
||
| getSpecService() { | ||
| return this.get(OAS_ENHANCER_SERVICE); | ||
| } | ||
| } | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.