Skip to content
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

target parameter of raiseIntent does not correspond to name of AppMetadata #156

Closed
rikoe opened this issue Jan 22, 2020 · 1 comment
Closed
Labels
api FDC3 API Working Group
Milestone

Comments

@rikoe
Copy link
Contributor

rikoe commented Jan 22, 2020

raiseIntent as defined as follows:

raiseIntent(intent: string, context: Context, target?: string): Promise<IntentResolution>;

AppMetadata as returned by findIntentsByContext as defined as follows:

interface AppMetadata {
  name: string;
}

The intent (har-har) is that you can use the app identifier returned by the discovery to target a specific app for raising an intent. But if AppMetadata returns a "name", this cannot be done, instead the unique app identifier should be use for the target parameter of raiseIntent, but it is not returned.

@rikoe rikoe added the api FDC3 API Working Group label Jan 22, 2020
@rikoe rikoe added this to the 1.1 milestone Jan 22, 2020
@rikoe rikoe added the 1.1 label Jan 22, 2020
rikoe added a commit to rikoe/FDC3 that referenced this issue Jan 22, 2020
@rikoe
Copy link
Contributor Author

rikoe commented Jan 23, 2020

Closing, as name is the correct field to use with raiseIntent, I was confused.

@rikoe rikoe closed this as completed Jan 23, 2020
rikoe added a commit to rikoe/FDC3 that referenced this issue Jan 25, 2020
rikoe added a commit to rikoe/FDC3 that referenced this issue Jan 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api FDC3 API Working Group
Projects
None yet
Development

No branches or pull requests

1 participant