Drop support for wildcard capability qualifiers
danielwiehl opened this issue · 0 comments
Describe the bug
The idea of the qualifier is to distinguish different capabilities of the same type but not to declare slots for passing data. The qualifier should be static. For passing data, a capability should declare optional or required parameters. Parameters do not affect the intent routing, unlike the qualifier.
To have a consistent way of passing data via parameters rather than qualifiers, we plan to drop support for wildcard qualifiers. This only affects capability qualifiers, not intention qualifiers or qualifiers to look up the manifest registry. For intention qualifiers, the concept of declaring wildcards is crucial so that an intention can match multiple capabilities.
For more information about the parameters, see the description of the capability: https://scion-microfrontend-platform-developer-guide.vercel.app/#chapter:intention-api:capability.