IOutboundParameterTransformer removed in a version that only updated the Minor version 2.2.0 to 2.3.0 but also seems to appear in main branch in same place

[anthony-dewhirst-dfe]

I updated nuget package Microsoft.AspNetCore.Routing.Abstractions from 2.2.0 to 2.3.0 to find that the interface Microsoft.AspNetCore.Routing.IOutboundParameterTransformer was no longer in the package.

Firstly, this should then be a Major version update as it's a breaking change, but I also don't quite understand as I can see it on the main branch in github:
https://github.com/dotnet/aspnetcore/blob/main/src/Http/Routing.Abstractions/src/IOutboundParameterTransformer.cs

I might be missing something?

[huoyaoyuan]

ASP.NET 2.3 is just a renaming of 2.1. It doesn't have superset feature than 2.2. See https://devblogs.microsoft.com/dotnet/servicing-release-advisory-aspnetcore-23/

[anthony-dewhirst-dfe]

That's a great link.
Still unsure why 2.3 has breaking changes over 2.2 then?
To be honest, we only use this to "slugify" the routing names. We are targeting standard2.0

/// <summary>
/// Transforms route names to lowercase and split on casing to enable more readable urls.
/// </summary>
public class SlugifyParameterTransformer : IOutboundParameterTransformer
{
    /// <inheritdoc cref="IOutboundParameterTransformer.TransformOutbound"/>
    public string TransformOutbound(object value)
    {
        if (value == null)
        {
            return null;
        }

        return Regex.Replace(value.ToString(),
            "([a-z])([A-Z])",
            "$1-$2",
            RegexOptions.CultureInvariant,
            TimeSpan.FromMilliseconds(100)).ToLowerInvariant();
    }
}

Are there other ways we can be doing this?

[huoyaoyuan]

Still unsure why 2.3 has breaking changes over 2.2 then?

Because 2.3 is actually 2.1, which doesn't "change over" 2.2. 2.2 changed over 2.1.

Are there other ways we can be doing this?

You can better ask at https://github.com/dotnet/aspnetcore .

[martincostello]

I don't have a link to hand pointing to anything that says this specifically, but .NET doesn't follow strict SemVer.

As said previously, .NET Core 2.3 is just a "rebranding" of .NET Core 2.1, and doesn't build on top of 2.2.