@voxgig/apidef 8.2.0 → 8.2.1
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/model/apidef.aon +15 -10
- package/package.json +1 -1
package/model/apidef.aon
CHANGED
|
@@ -128,17 +128,22 @@ main: kit: entity: &: {
|
|
|
128
128
|
var?: string
|
|
129
129
|
} ]
|
|
130
130
|
|
|
131
|
-
#
|
|
131
|
+
# NO TOMBSTONE FOR `parts` HERE, and this is load-bearing.
|
|
132
132
|
#
|
|
133
|
-
#
|
|
134
|
-
#
|
|
135
|
-
#
|
|
136
|
-
#
|
|
137
|
-
#
|
|
138
|
-
#
|
|
139
|
-
#
|
|
140
|
-
#
|
|
141
|
-
|
|
133
|
+
# 8.2.0 declared `parts?: null` so that a model generated by apidef
|
|
134
|
+
# <= 8.1 would fail to unify rather than take the empty `segments`
|
|
135
|
+
# default and send every request to the API root. It caught exactly
|
|
136
|
+
# that, and it also BRICKED the upgrade: a project's checked-in
|
|
137
|
+
# `.sdk/model/entity/*.aon` IS the input to the tool that rewrites it,
|
|
138
|
+
# and voxgig-model unifies before it runs apidef's build. So the stale
|
|
139
|
+
# file blocked the regeneration that would have removed it, with no
|
|
140
|
+
# supported way out — `voxgig-apidef` is still a stub.
|
|
141
|
+
#
|
|
142
|
+
# A schema cannot police its own migration. The guard belongs where a
|
|
143
|
+
# stale point would actually do harm: sdkgen reads the path through one
|
|
144
|
+
# helper, and that helper refuses a point carrying `parts` and no
|
|
145
|
+
# `segments`. Same defect caught, at generation time, without
|
|
146
|
+
# deadlocking the regeneration.
|
|
142
147
|
|
|
143
148
|
# GraphQL wire data: the precomputed operation document plus the
|
|
144
149
|
# variable bindings and (for list ops) the pagination descriptor.
|