-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FFI calls > Support generators for async message #338
Comments
Reify doesn't support synchronous messages and a bunch of things. I think you're best using the message-related iterators to extract these values. The method should probably be marked as deprecated. |
I don't know how to use those iterators methods yet. I can't find any example code. Look like there are no language using those methods yet? btw thanks for the suggestion. |
No worries! Btw I use it in Go here: https://github.com/pact-foundation/pact-go/blob/master/internal/native/message_server.go#L397-L519. |
Using these methods:
I'm able to get the message content, but it's exactly the same with the result from Plus I have a panic
|
pactffi_message_reify
I'm able to use those iterator methods, but there 2 small problems:
I also updated |
Closed as implemented |
Nice one! I'm interested - does this work on synchronous messages also (both the request and/or response side)? |
I didn't touch on synchronous message FFI calls. But I have a quick look at
Currently I can't implement synchronous message in compatibility suite in PHP so I can't test it. |
oh yes, I know they support generators. I guess I was asking if you could use |
No, I don't think so. |
These scenarios in compatibility suite indicate that generators are supported for async message on consumer side:
But currently I think generators are not working when using this
pactffi_message_reify
FFI call.The text was updated successfully, but these errors were encountered: