@scalar/fastify-api-reference 1.25.52 → 1.25.54

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,15 @@
1
1
  # @scalar/fastify-api-reference
2
2
 
3
+ ## 1.25.54
4
+
5
+ ## 1.25.53
6
+
7
+ ### Patch Changes
8
+
9
+ - fb798c8: chore: make OpenAPI document URLs the default, deprecated `content`
10
+ - Updated dependencies [fb798c8]
11
+ - @scalar/types@0.0.18
12
+
3
13
  ## 1.25.52
4
14
 
5
15
  ## 1.25.51
package/README.md CHANGED
@@ -40,37 +40,11 @@ fastify.register(require('@scalar/fastify-api-reference'), {
40
40
  })
41
41
  ```
42
42
 
43
- With [@fastify/swagger](https://github.com/fastify/fastify-swagger) you can even generate your OpenAPI documents from the registered routes and directly pass it to the plugin:
43
+ With [@fastify/swagger], we’re picking it up automatically, so this would be enough:
44
44
 
45
45
  ```ts
46
46
  await fastify.register(require('@scalar/fastify-api-reference'), {
47
47
  routePrefix: '/reference',
48
- configuration: {
49
- spec: {
50
- content: () => fastify.swagger(),
51
- },
52
- },
53
- })
54
- ```
55
-
56
- Actually, we’re picking it up automatically, so this would be enough:
57
-
58
- ```ts
59
- await fastify.register(require('@scalar/fastify-api-reference'), {
60
- routePrefix: '/reference',
61
- })
62
- ```
63
-
64
- Or, if you just have a static OpenAPI spec, you can directly pass it, too:
65
-
66
- ```ts
67
- await fastify.register(require('@scalar/fastify-api-reference'), {
68
- routePrefix: '/reference',
69
- configuration: {
70
- spec: {
71
- content: { … }
72
- },
73
- },
74
48
  })
75
49
  ```
76
50