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
A few classes have faulty C++/Qt code generation, specifically, those that are unions containing one or more structs: The generated code expects the structs to be rendered in JSON as standalone objects, but the Stone specification (https://github.com/dropbox/stone/blob/main/docs/json_serializer.rst#union) explicitly (though illogically) states that each struct field is rendered individually in the union object alongside its tag. The example that affects my code is UploadWriteFailed (struct) inside UploadError (union) - see https://github.com/dropbox/dropbox-api-spec/blob/main/files.stone lines 767ff.: The path union member is a struct, but that struct's one field (reason) is rendered as its own object alongside".tag": "path", not encapsulated inside a "path": {...} object as your generated code expects.
A few classes have faulty C++/Qt code generation, specifically, those that are unions containing one or more structs: The generated code expects the structs to be rendered in JSON as standalone objects, but the Stone specification (https://github.com/dropbox/stone/blob/main/docs/json_serializer.rst#union) explicitly (though illogically) states that each struct field is rendered individually in the union object alongside its tag. The example that affects my code is UploadWriteFailed (struct) inside UploadError (union) - see https://github.com/dropbox/dropbox-api-spec/blob/main/files.stone lines 767ff.: The path union member is a struct, but that struct's one field (reason) is rendered as its own object alongside ".tag": "path", not encapsulated inside a "path": {...} object as your generated code expects.
See this conversation with a Dropbox employee, who explains it well: https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Documentation-UploadError-marked-as-open-union-is-datatype-with/m-p/467202/highlight/true#M1556
The text was updated successfully, but these errors were encountered: