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
Multipart request example in API Blueprint results in body asset containing newlines formed by \n only. However, such asset isn't valid and usable as raw HTTP payload, all infrastructure counts with \r\n being in place.
Dredd currently fixes this, but I consider it as a workaround. I think the API Blueprint format should take care of this and to provide user with a correct, raw HTTP representation of a body. I guess if other API description formats support multipart, let's say in some declarative way, or if #100 gets implemented in API Blueprint, the API Elements asset should contain the body with \r\n, not with \n.
This was previously a core part of Dredd. It belongs to Dredd Transactions
though as it's a format-specific bug fix. Ideally, Dredd shouldn't need
to know anything about the specifics of formats, Dredd Transactions
should provide a uniform interface.
apiaryio/api-blueprint#401
Multipart request example in API Blueprint results in body asset containing newlines formed by
\n
only. However, such asset isn't valid and usable as raw HTTP payload, all infrastructure counts with\r\n
being in place.Dredd currently fixes this, but I consider it as a workaround. I think the API Blueprint format should take care of this and to provide user with a correct, raw HTTP representation of a body. I guess if other API description formats support multipart, let's say in some declarative way, or if #100 gets implemented in API Blueprint, the API Elements asset should contain the body with
\r\n
, not with\n
.Example API Blueprint:
Resulting asset:
Expected resulting asset:
The text was updated successfully, but these errors were encountered: