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
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Use an overrides file to customize your API definition without modifying the ori
9
9
* You need different configurations for SDKs versus documentation
10
10
11
11
<Note>
12
-
While you can also embed Fern extensions directly in your API specification, using overrides files is the recommended approach as it keeps your original spec clean and separates concerns.
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.
13
13
</Note>
14
14
15
15
## Implement overrides
@@ -31,8 +31,7 @@ fern/
31
31
<Note> The format of the overrides file is independent from the spec. For example, even if your OpenAPI spec is in JSON format, you can write the overrides in yaml. </Note>
32
32
33
33
</Step>
34
-
<Steptitle="Add customizations">
35
-
34
+
<Steptitle="Customize your spec with Fern extensions">
36
35
```yml title="overrides.yml" {4-5}
37
36
paths:
38
37
/users:
@@ -172,4 +171,4 @@ Learn more about the customizations you can make for each definition:
0 commit comments