-
Notifications
You must be signed in to change notification settings - Fork 132
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
Intent resolution data clarification #219
Comments
Good to hear that it is looked at! Is there a draft spec of the 1.2 version which is publicly available ? |
Nope, it is relatively early on in the process. See #201 for a recent straw man proposal about how this could work. Please join in on the discussion, and attend our standard working group meetings! |
Closing in favour of #201 |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Question Area
[ ] App Directory
[x] API
[x] Context Data
[x] Intents
[ ] Use Cases
[ ] Other
Question
Referring to the API specification, an intent resolution may contain a payload attached to it. This piece of data, as far as I understand, would have been computed by the handler of that intent.
Reference:
https://fdc3.finos.org/docs/1.0/api/api-spec#resolution-object
However, looking at the specification of Intent listener it is not clear to me how does one Intent handler actual does provide this payload back.
Reference:
https://fdc3.finos.org/docs/1.0/api/DesktopAgent#addintentlistener
Could you please clarify that area?
The text was updated successfully, but these errors were encountered: