Remove OfXAttribute.Order. The next big thing!

[quyvu01]

Hi everyone,
I’d like to share an update on the next big improvement in OfX: I’m removing the OfXAttribute.Order property.
In previous versions, we had to manually specify Order to help OfX understand the mapping sequence. For example:

public sealed class SomeDataResponse
{
    public string Id { get; set; }
    public string UserId { get; set; }

    [UserOf(nameof(UserId))]
    public string UserName { get; set; }

    [UserOf(nameof(UserId), Expression = "ProvinceId")]
    public string ProvinceId { get; set; }

    [ProvinceOf(nameof(ProvinceId), Expression = "CountryId", Order = 1)]
    public string CountryId { get; set; }

    [CountryOf(nameof(CountryId), Expression = "Provinces[0 asc Name].Name", Order = 2)]
    public string Province { get; set; }

    // Add other properties as needed
}

With the upcoming change, the Order attribute is no longer necessary because OfX can now build the dependency graph automatically based on the references between properties.
Thank you for your continued support and love for OfX. This change will make OfX cleaner, smarter, and even more useful for you all!