RelationPropertySchema and RelationUpdatePropertySchema are broken.

[gehongyan]

Describe the bug
In Notion API version 2022-06-28, database relations would have a type of single_property and dual_property.
This commit updated the changes on RelationProperty for models, but RelationPropertySchema and RelationUpdatePropertySchema for request parameters were not updated, hence the failure of related requests.

Related Notion changelog: https://developers.notion.com/page/changelog#database-relations-have-a-type-of-single_property-and-dual_property

[chrissimon-au]

This is also affecting me... @gehongyan , I'm wondering if you found a workaround to make use of until 4.3.0 is published?

[chrissimon-au]

I was able to find a workaround using the underlying Rest client and passing in a dictionary to the body that matches the currently correct schema:

{
   "properties": {
      "<name>": {
         "relation": {
            "database_id": "<id>",
            "dual_property": { }
         }
      }
   }
}

So I use the typed API to create the database and most properties, then a custom Rest client call to add the relation property - this seems like a good balance and hopefully easy to revert once 4.3.0 is out.

[gehongyan]

This is also affecting me... @gehongyan , I'm wondering if you found a workaround to make use of until 4.3.0 is published?

My current workaround:

/// <summary>
///     Fixture of <see cref="Notion.Client.RelationUpdatePropertySchema.RelationInfo"/>
///     for updating single property relation.
/// </summary>
public class SinglePropertyUpdateRelationInfo : RelationUpdatePropertySchema.RelationInfo
{
    /// <summary>
    ///     Gets the type representing <c>single_property</c>.
    /// </summary>
    [Newtonsoft.Json.JsonProperty("type")]
    public string Type => "single_property";

    /// <summary>
    ///     Gets or sets the properties of a single property.
    /// </summary>
    [Newtonsoft.Json.JsonProperty("single_property")]
    public Dictionary<string, object> SingleProperty { get; set; }

    [Newtonsoft.Json.JsonIgnore]
    [Obsolete("Not a valid field for current endpoint.")]
    public new string SyncedPropertyId { get; set; }

    [Newtonsoft.Json.JsonIgnore]
    [Obsolete("Not a valid field for current endpoint.")]
    public new string SyncedPropertyName { get; set; }
}

/// <summary>
///     Fixture of <see cref="Notion.Client.RelationUpdatePropertySchema.RelationInfo"/>
///     for updating dual property relation.
/// </summary>
public class DualPropertyUpdateRelationInfo : RelationUpdatePropertySchema.RelationInfo
{
    /// <summary>
    ///     Gets the type representing <c>dual_property</c>.
    /// </summary>
    [JsonProperty("type")]
    public string Type => "dual_property";

    /// <summary>
    ///     Gets or sets the properties of a dual property.
    /// </summary>
    [JsonProperty("dual_property")]
    public Dictionary<string, object> DualProperty { get; set; }

    [Newtonsoft.Json.JsonIgnore]
    [Obsolete("Not a valid field for current endpoint.")]
    public new string SyncedPropertyId { get; set; }

    [Newtonsoft.Json.JsonIgnore]
    [Obsolete("Not a valid field for current endpoint.")]
    public new string SyncedPropertyName { get; set; }
}

Then I can update the properties with:

new DatabasesUpdateParameters
{
    Properties = new Dictionary<string, IUpdatePropertySchema>
    {
        ["ColumnName"] = new RelationUpdatePropertySchema
        {
            Relation = new SinglePropertyUpdateRelationInfo
            {
                SingleProperty = new Dictionary<string, object>(),
                DatabaseId = Guid.Parse(databaseId)
            }
        }
    }
};