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
// Aux contains out-of-band data, such as digests for push signing and image id after building.
Aux*json.RawMessage`json:"aux,omitempty"`
}
We should have a look at those;
If they're all describing JSONMessage, should they all be identical (or same type)?
Possibly some endpoints don't use all fields, and due to the use of omitempty they are "different types" (from an API response perspective), although possibly that could be described with -x-nullable
None of them describe the ProgressMessage (progress in JSON) and ErrorMessage (error in JSON) fields to be deprecated
ProgressMessage appears to be marked as deprecated in 597e0e6 (Refactor stream #2945) - although no mention of the deprecation
JSONMessage
;moby/pkg/jsonmessage/jsonmessage.go
Lines 135 to 151 in d73aba2
We should have a look at those;
JSONMessage
, should they all be identical (or same type)?omitempty
they are "different types" (from an API response perspective), although possibly that could be described with-x-nullable
ProgressMessage
(progress
in JSON) andErrorMessage
(error
in JSON) fields to be deprecatedProgressMessage
appears to be marked as deprecated in 597e0e6 (Refactor stream #2945) - although no mention of the deprecationErrorMessage
was marked deprecated in 3043c26 (Do not require login unless 401 is received on push #1298) - need to check if there's actually still code using the field.Originally posted by @thaJeztah in #44061 (comment)
The text was updated successfully, but these errors were encountered: