> For the complete documentation index, see [llms.txt](https://cheronantoine.gitbook.io/ph-d/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cheronantoine.gitbook.io/ph-d/api-client-evolution/discussions.md).

# Discussions

## About change 2 of the evolution space

In the example, two parameters are merged into a composite object, which is named a type change.

{% hint style="warning" %}
**Research question identified**

How to automatically/programmatically differentiate type changes from additions or/and removals?
{% endhint %}

The following example illustrates a case that highlights the problem of differentiating changes from additions or/and removals. Handling such a case is easy for humans but how would a machine do it?

{% tabs %}
{% tab title="v1.0" %}

```javascript
{
  id: 1234,
  title: "Buy groceries",
  due_date: "2020-01-01",
  due_time: "8:00"
}
```

{% endtab %}

{% tab title="v2.0 (type change)" %}

```javascript
{
  id: 1234,
  title: "Buy groceries",
  due_details: {
    due_date: "2020-01-01",
    due_time: "8:00"
  }
}
```

{% endtab %}

{% tab title="v2.0 (not type change)" %}

```javascript
{
  id: 1234,
  title: "Buy groceries",
  subtasks: [
    { 
      title: "Tomatoes",
      due_details: {
        due_date: "2020-01-01",
        due_time: "8:00"
      }
    },
    {
      title: "Ham",
      due_details: {
        due_date: "2020-01-03",
        due_time: "12:00"
      }
    }
  ]
}
```

{% endtab %}
{% endtabs %}

{% hint style="danger" %}
This is something the currently designed approach is not able to address.

Is it its role? By not trying to make reasonings about operation parameters nor automatically fulfilling parameters value, and suggesting to generate a form that humans will fulfill, such a change is not breaking the UI.

May server-provided parameters help? As it is done in my approach to provide technical ids.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cheronantoine.gitbook.io/ph-d/api-client-evolution/discussions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.