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
In order for taps and targets to confidently support spec extensions in a backwards compatible way, we'll need a way to taps and targets to advertise their capabilities and list of supported settings.
The SDK handles this with (--about and --about --format=json) but we should agree on a standard (like the --discover flag) which the community can rely on.
Note: The SDK also uses --about to advertise supported config settings. We can discuss that topic here as well, but we may split into a separate issue if scope is too broad.
The text was updated successfully, but these errors were encountered:
aaronsteers
changed the title
Self-declared tap and target capabilities (--about support in CLI)
Self-declared capabilities (--about support in CLI)
Sep 27, 2021
aaronsteers
changed the title
Self-declared capabilities (--about support in CLI)
Discoverable capabilities and list of setting (--about support in CLI)
Sep 27, 2021
aaronsteers
changed the title
Discoverable capabilities and list of setting (--about support in CLI)
Discoverable capabilities setting (--about support in CLI)
Sep 27, 2021
aaronsteers
changed the title
Discoverable capabilities setting (--about support in CLI)
Discoverable capabilities and settings (--about support in CLI)
Sep 27, 2021
In order for taps and targets to confidently support spec extensions in a backwards compatible way, we'll need a way to taps and targets to advertise their capabilities and list of supported settings.
The SDK handles this with (
--about
and--about --format=json
) but we should agree on a standard (like the--discover
flag) which the community can rely on.Note: The SDK also uses
--about
to advertise supported config settings. We can discuss that topic here as well, but we may split into a separate issue if scope is too broad.The text was updated successfully, but these errors were encountered: