Skip to content

Overhaul design to handle changes between spec versions #569

Open
@stephentoub

Description

@stephentoub

We're already seeing breaking changes finding their way into the spec. For example, the 06-18 spec declares "declined" as an elicitation response, whereas the current draft changes that to "rejected". The current sampling result contains only a single content whereas there's a plan to change it to be an array. Etc. We need to find a way to keep the APIs as free from breaking changes as possible while supporting correctly working with any negotiated protocol with the current remote endpoint.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions