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
This is related to my other Question below in the "issues" section because we can't upload a Multipart form(binary) and we currently cannot parse Data(binary) objects either. We receive an error:
"failed - Error preparing pact! A key or value in the structure does not conform to 'Encodable' protocol. The element attempted to encode: 1 bytes"
Data does not conform to Encodable, which makes sense since it's binary and does not need to be translated, however, it shouldn't have that check. Is this something y'all are looking into?
I believe it's this file that is causing the issue since it's always trying to encode the body:
Sources/Model/Response.swift
The text was updated successfully, but these errors were encountered:
There’s major refactoring happened a while back already but hasn’t been cleaned up and made release “worthy” due to lack of time. But that’s changed these days and I’ll have time to have a look and hopefully bring that refactoring piece of work closer to new version release.
Most of the Pact generation responsibility will be pushed down to pact_ffi (core pact functionality written in Rust) and potentially should allow such tests.
I’d love your help verifying some of these use cases work in the upcoming few weeks. I’ll make myself more available in the Pact Foundation slack.
🌎 Environment
💬 Description
This is related to my other Question below in the "issues" section because we can't upload a Multipart form(binary) and we currently cannot parse Data(binary) objects either. We receive an error:
"failed - Error preparing pact! A key or value in the structure does not conform to 'Encodable' protocol. The element attempted to encode: 1 bytes"
Data does not conform to Encodable, which makes sense since it's binary and does not need to be translated, however, it shouldn't have that check. Is this something y'all are looking into?
I believe it's this file that is causing the issue since it's always trying to encode the body:
Sources/Model/Response.swift
The text was updated successfully, but these errors were encountered: