Column order not scaffolded as attribute

See this in 7.0 RC1, when using DataAnnotations

        modelBuilder.Entity<Shipper>(entity =>
        {
            entity.Property(e => e.ShipperId).HasColumnOrder(0);
            entity.Property(e => e.CompanyName).HasColumnOrder(1);
            entity.Property(e => e.Phone).HasColumnOrder(2);
        });

public partial class Shipper
{
    [Key]
    [Column("ShipperID")]
    public int ShipperId { get; set; }

    [StringLength(40)]
    public string CompanyName { get; set; } = null!;

    [StringLength(24)]
    public string? Phone { get; set; }

    [InverseProperty("ShipViaNavigation")]
    public virtual ICollection<Order> Orders { get; } = new List<Order>();
}

I was hoping for this:

public partial class Shipper
{
    [Key]
    [Column("ShipperID", Order = 0)]
    public int ShipperId { get; set; }

    [StringLength(40)]
    [Column("CompanyName", Order = 1)]
    public string CompanyName { get; set; } = null!;

    [StringLength(24)]
    [Column("Phone", Order = 2)]
    public string? Phone { get; set; }

    [InverseProperty("ShipViaNavigation")]
    public virtual ICollection<Order> Orders { get; } = new List<Order>();
}

[bricelam]

Yeah, we’re not supposed to scaffold that. We just use it to sort the CLR properties. (Which would then be used by Migrations to re-create the columns in the same order.)

[ajcvickers]

Also surprised with scaffold this. I don’t think we should by default. /cc @bricelam