Enhance typed client methods and validation

[mpartipilo]

Improve type safety and validation for typed clients, add integration and unit tests, and optimize the test workflow. Introduce optional client-side schema validation and enhance the TypeValidator to support anonymous types. Refactor code for better performance and readability.

[orca-security-eu]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Secrets	0   0   0   0	View in Orca

[g-despot]

Does this correctly handle compatibility between float/double in C# and numbers in Weaviate? Or for example C# enums to Weaviate text? Can also be added in future releases

[mpartipilo]

If you give me more concrete use cases I can create tests for these scenarios

[g-despot]

Tried these additional tests in TestTypeValidator.cs:

    // Models for compatibility tests
    private class ProductFloat { public float Price { get; set; } }
    private class ProductDecimal { public decimal Price { get; set; } }
    private class OrderLong { public long Quantity { get; set; } }
    private enum TaskStatusEnum { Pending, InProgress, Completed }
    private class UserTask { public TaskStatusEnum Status { get; set; } }

    [Theory]
    [InlineData(typeof(ProductFloat))]
    [InlineData(typeof(ProductDecimal))]
    public void ValidateType_NumberCompatibility_IsValid(Type type)
    {
        // Arrange
        var schema = new CollectionConfig
        {
            Name = "Product",
            Properties =
            [
                new Property { Name = "price", DataType = [DataType.Number] }
            ]
        };
        var validator = TypeValidator.Default;

        // Act
        var result = validator.ValidateType(type, schema);

        // Assert
        Assert.True(result.IsValid);
        Assert.Empty(result.Errors);
    }

    [Fact]
    public void ValidateType_IntCompatibility_IsValid()
    {
        // Arrange
        var schema = new CollectionConfig
        {
            Name = "Order",
            Properties =
            [
                new Property { Name = "quantity", DataType = [DataType.Int] }
            ]
        };
        var validator = TypeValidator.Default;

        // Act
        var result = validator.ValidateType<OrderLong>(schema);

        // Assert
        Assert.True(result.IsValid);
        Assert.Empty(result.Errors);
    }

    [Fact]
    public void ValidateType_EnumCompatibility_IsValid()
    {
        // Arrange
        var schema = new CollectionConfig
        {
            Name = "UserTask",
            Properties = new List<Property>
            {
                new Property { Name = "status", DataType = new List<string> { DataType.Text } }
            }
        };
        var validator = TypeValidator.Default;

        // Act
        var result = validator.ValidateType<UserTask>(schema);

        // Assert
        Assert.True(result.IsValid);
        Assert.Empty(result.Errors);
    }

The first two worked 👏🏻 but the third one doesn't ValidateType_EnumCompatibility_IsValid. Maybe it makes sense to add enums mapping to text in DataTypeForType

[mpartipilo]

Yes, that's a very good idea.

[mpartipilo]

I updated the PR with the logic to handle Enums in both numerical and string forms. Check it out!

[orca-security-eu]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Infrastructure as Code	0   0   0   0	View in Orca
Passed	SAST	0   0   0   0	View in Orca
Passed	Secrets	0   0   0   0	View in Orca
Passed	Vulnerabilities	0   0   0   0	View in Orca