Skip to content

Commit d9b4865

Browse files
Grammar and syntax adjustments
Co-authored-by: Johannes Schobel <[email protected]>
1 parent ff11001 commit d9b4865

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

content/techniques/versioning.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -107,13 +107,14 @@ For example, if an incoming request specifies it supports versions `1`, `2`, and
107107
If versions `[3, 2, 1]` are extracted, but routes only exist for version `2` and `1`, the route that matches version `2`
108108
is selected (version `3` is automatically ignored).
109109

110-
> warning **Notice** Selecting the highest matched version based on the array returned from `extractor`
110+
> warning **Notice** Selecting the highest matching version based on the array returned from `extractor`
111111
> **does not reliably work** with the Express adapter due to design limitations. A single version (either a string or
112-
> array of 1 element) works just fine in Express. Fastify correctly supports both highest matched version
112+
> array of 1 element) works just fine in Express. Fastify correctly supports both highest matching version
113113
> selection and single version selection.
114114
115115
To enable **Custom Versioning** for your application, create an `extractor` function and pass it into your application
116116
like so:
117+
117118
```typescript
118119
@@filename(main)
119120
// Example extractor that pulls out a list of versions from a custom header and turns it into a sorted array.

0 commit comments

Comments
 (0)