Add Agent.definitions - #104
Draft
Fannon wants to merge 2 commits into
Draft
Conversation
|
Member
Author
|
Unsure if we should do it, honestly. It feels like we make it too easy to put the definition to the wrong place, as usually the detailed definition files are protocol dependent and therefore belong to the API. On agent level, we might get away from adding enough labels, e.g. what we started with |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To be discussed if we need it, e.g. for Agent Extension Points Definition (which is independent from a particular exposed API of the agent).
Added
definitionsproperty toAgentresources to allow linking machine-readable agent definitionsAgentDefinitionobject withtype,mediaType,url,accessStrategies, andvisibilitypropertiestypefield accepts any valid Specification ID as an extensible enum