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
Is your feature request related to a problem? Please describe.
When modeling UI components via Intention API, the integrator typically issues an intent when the user interacts with that component. However, if there are other capabilities that match the qualifier of the capability, the intent is transported to them as well, leading to unexpected behavior.
Describe the solution you'd like
This intent should be transported exclusively to the provider of the capability, even if there are other capabilities that match the qualifier.
In this particular use case, I could imagine passing the capability identifier to the IntentClient instead of the type and qualifier.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When modeling UI components via Intention API, the integrator typically issues an intent when the user interacts with that component. However, if there are other capabilities that match the qualifier of the capability, the intent is transported to them as well, leading to unexpected behavior.
Describe the solution you'd like
This intent should be transported exclusively to the provider of the capability, even if there are other capabilities that match the qualifier.
In this particular use case, I could imagine passing the capability identifier to the
IntentClient
instead of thetype
andqualifier
.The text was updated successfully, but these errors were encountered: