Closed ghost closed 5 years ago
Hello,
First of all thank you for the PRs, I merged your first two. For this one, since it's changing the namings, it can break people's code and I don't know if I should release it as a pre-release or something, what do you think?
Hi, there are two ways of how this could be handled.
Step up to the next major version and inherit from the old class, like:
public class BreadcrumbsManager : BreadcrumbManager {}
and by using an overload for the UseBreadcrumbs()
method, both marked as [Obsolete]
. This allows the easier removal in one of the next versions.
Nevertheless, do you mind updating the NuGet package?
Done, it's validating for now.
SmartBreadcrumbs 2.0.0 comes with these changes.
⚠️ Breaking change!
This PR aligns the class and method names to common guidelines. For example, the extension method is called
UseBreadcrumbs
at the moment, which is normally used in theStartup.Configure()
method. However, this method requires theIServiceCollection
, which is usually done in theStartup.ConfigureServices()
method. However, in the latter, the method namingservices.Add..
is common.