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
One could argue about the term "JSON-Schema type" here, and rather say that in the first case, the text should say
Type of each property: glTFid
but with the caveat that glTFid does not appear in the property reference, but only in the schema reference. (It is listed as one of the "ignored types" when creating the property reference).
Or to put it that way: Iff there was a structure with
then it should not say object, but a link to buffer at this point. At least, I think that the current output is indeed the result of an attempt to exactly do this sort of cross-linking between types. (IIRC, there is no case where this is relevant for glTF - here, it will always be object in these cases - but I'm trying to get a better understanding for wetzel right now...)
@lexaknyazev You had assigned that to yourself - not sure whether that was intentional - but it should be addressed (together with #2165 ) in CesiumGS/wetzel#88 .
The
mesh.primitive.attributes
schema declaresand the
mesh.primitive.attributes
property reference shows this asIn contrast to that, the
extension
schema declaresand the property reference for this - which is inlined into all property references, for example, the
mesh.primitive.extensions
property reference - shows this asShouldn't this "type of each property" be
object
instead?(This came up via CesiumGS/wetzel#68 (comment) )
The text was updated successfully, but these errors were encountered: