[Bug]: ‼️ request-body-strict does not work properly.

[JerryNixon]

What happened?

Setting request-body-strict does not work properly.

Desired (Correct) behavior:

REST methods Put, Post, Patch entity payloads can include primary key properties. They are ignored.

Actual (incorrect) behavior:

Exception. Entity payloads including primary key properties result in exception.

Status

It should be noted that the desired behavior is the only reason for the setting.

Workaround

Developers using .NET (at least) must unceremoniously remove the primary key properties from their models before calls.

public async Task<Player> UpdateAsync(Player player)
{
    ArgumentNullException.ThrowIfNull(player);

    // remove primary key
    var node = JsonSerializer.SerializeToNode(player);
    node?.AsObject().Remove("id");

    var url = $"{baseUrl}/Id/{player.Id}";
    var response = await http.PutAsJsonAsync(url, node);
    var json = await response.Content.ReadAsStringAsync();
    var root = JsonSerializer.Deserialize<PlayerRoot>(json)
        ?? throw new Exception("Response Json is invalid.");
    return root.Players.Single();
}

This is what it should look like:

public async Task<Player> UpdateAsync(Player player)
{
    ArgumentNullException.ThrowIfNull(player);

    var url = $"{baseUrl}/Id/{player.Id}";
    var response = await http.PutAsJsonAsync(url, player);
    var json = await response.Content.ReadAsStringAsync();
    var root = JsonSerializer.Deserialize<PlayerRoot>(json)
        ?? throw new Exception("Response Json is invalid.");
    return root.Players.Single();
}

[aaronburtle]

After some investigation it seems that the issue is really with auto-generated primary keys. These operations work with request-body-strict but not if the primary key is autogenerated. Fix is incoming.