Suggestion: Expose a parameter of `ShouldMatch` for `<NavLink />`

[newbienewbie]

Is your feature request related to a problem? Please describe.

I want to custom the matching behavior of <NavLink />.

Let's say we want to process a url with a hash(See this thread on SO) :

http://localhost/#an-element-id

Sometimes we might think this url matches http://localhost , while some other users don't think so.

It would be great if we are allowed to custom this matching behavior. Usually, we can custom by inheritance or composition. However, the matching logic is hardcoded for the present.

1. There's no public/protected ShouldMatch(string) method exposed. So it's difficult to achieve it by inheritance
2. There's no ShouldMatch parameter exposed. It would be great if we can pass a ShouldMatch [Parameter] to this component.

Describe the solution you'd like

Expose a [Parameter] of ShouldMatch(string):

• if user provides such a parameter, use it.
• Otherwise, use the default logic.

[mkArtakMSFT]

We've moved this issue to the Backlog milestone. This means that it is not going to happen for the coming release. We will reassess the backlog following the current release and consider this item at that time. However, keep in mind that there are many other high priority features with which it will be competing for resources.

[TanayParikh]

Just confirming my understanding of your proposal; this ShouldMatch would be a:

        /// <summary>
        /// Gets or sets an action facilitating custom matching behavior.
        /// </summary>
        [Parameter]
        public Action<string, bool> ShouldMatch { get; set; }

wouldn't this conflict with the NavLinkMatch parameter?

aspnetcore/src/Components/Web/src/Routing/NavLink.cs

Lines 48 to 52 in c17ce43

	/// <summary>
	/// Gets or sets a value representing the URL matching behavior.
	/// </summary>
	[Parameter]
	public NavLinkMatch Match { get; set; }

cc/ @javiercn @SteveSandersonMS

[SteveSandersonMS]

wouldn't this conflict with the NavLinkMatch parameter?

Yes, good point. The ShouldMatch callback would be like a more generalised version of the Match parameter, in that it lets you implement your own matching strategy instead of limiting you to the predefined choices in an enum.

We'd have to define a rule like "if you have supplied a ShouldMatch callback, you must not also specify Match since it would not be used".