You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: fern/products/api-def/pages/overrides.mdx
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,13 +3,15 @@ title: Overrides
3
3
description: Customize your API definition using a separate overrides file.
4
4
---
5
5
6
-
Use an overrides file to customize your API definition without modifying the original spec. This is useful when:
6
+
Use an overrides file to customize your OpenAPI, AsyncAPI, OpenRPC, or gRPC definition without modifying the original spec. This is useful when:
7
7
8
8
* Your API specification is auto-generated from server code
9
9
* You need different configurations for SDKs versus documentation
10
10
11
+
Overrides are available for OpenAPI, AsyncAPI, OpenRPC, and gRPC specifications. They are not needed for [Fern Definition](/api-definitions/ferndef/overview) since you can directly edit those files.
12
+
11
13
<Note>
12
-
While you can also embed [Fern extensions](https://buildwithfern.com/learn/api-definitions/openapi/extensions/overview) directly in your API specification, using overrides files is the recommended approach as it keeps your original spec clean and separates concerns.
14
+
While you can also embed [Fern extensions](/api-definitions/overview/overrides#definition-specific-extensions) directly in your API specification, using overrides files is the recommended approach as it keeps your original spec clean and separates concerns.
13
15
</Note>
14
16
15
17
## Implement overrides
@@ -32,6 +34,9 @@ fern/
32
34
33
35
</Step>
34
36
<Steptitle="Customize your spec with Fern extensions">
37
+
38
+
For OpenAPI, AsyncAPI, and OpenRPC, and gRPC, you can use [Fern's extensions](/api-definitions/overview/overrides#definition-specific-extensions) to apply customizations.
39
+
35
40
```yml title="overrides.yml" {4-5}
36
41
paths:
37
42
/users:
@@ -158,9 +163,9 @@ groups:
158
163
version: 0.8.8
159
164
```
160
165
161
-
## Definition-specific customizations
166
+
## Definition-specific extensions
162
167
163
-
Learn more about the customizations you can make for each definition:
168
+
Learn more about the Fern extensions you can use to customize your definition:
0 commit comments