Addressed documentation issues in the custom version table configuration section per issue #2217.

Changes

• Property descriptions: Corrected IVersionTableMetaData property descriptions to accurately reflect that columns store information for each migration, not just the last one
• Implementation examples: Added comprehensive examples showing both direct IVersionTableMetaData implementation and inheritance from DefaultVersionTableMetaData with proper constructor patterns
• Registration patterns: Documented the difference between .WithVersionTable() for direct implementations and .AddScoped<IVersionTableMetaData, T>() for DI-based registrations

Examples Added

Direct implementation:

[VersionTableMetaData]
public class CustomVersionTable : IVersionTableMetaData
{
    public string TableName => "CustomVersionInfo";
    // ... other properties
}

services.ConfigureRunner(rb => rb.WithVersionTable(new CustomVersionTable()))

Inheritance pattern:

[VersionTableMetaData]
public class CustomVersionTable : DefaultVersionTableMetaData
{
    public CustomVersionTable(IConventionSet conventionSet, IOptions<RunnerOptions> runnerOptions) 
        : base(conventionSet, runnerOptions) { }
    
    public override string TableName => "CustomVersionInfo";
    public override string SchemaName => "migrations";
}

services.AddScoped<IVersionTableMetaData, CustomVersionTable>();

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.