-
Notifications
You must be signed in to change notification settings - Fork 29
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
spec.yaml or README.md out of date #103
Comments
I think this is correct. In this case "bytes" are passed in as a string encded as hex or base64. |
so it is that the README.md should be updated, right? Because an example in the readme uses the "stringifiedJSON" value for the "payloadType" property, at https://github.com/hyperledger/firefly-fabconnect#json-data-support-in-events |
Sorry I'm not understanding or seeing anything that is not correct here. "Stringified JSON" is just a string so it's still valid. |
when I put the value "stringifiedJSON" to the property "payloadType", this is the response that the endpoint "http://localhost:3000/subscriptions" returns: |
It only lets me pass the values "string" or "json" |
Ah okay, I get it. Sorry I was slow to understand this one! I think the readme can be changed to just say "string" there instead. |
Exactly, sorry if I didn't explain well. My English is not very good |
pull-request: #104 |
Hi @nguyer, @jimthematrix
The "payloadType" property of the "SubscriptionInfo" structure in internal/events/api/event.go accepts the data types "bytes", "string" or "stringifiedJSON/json".
or is the README.md the one that is not updated?
But in the spec.yaml only "json" and "string" are accepted.
The text was updated successfully, but these errors were encountered: