Task - Create a reusable button/anchor tag attribute selected component for an Angular library, with as much of the logic for the behavior tied up in the component itself not on the HTML markup.
HTML markup should be as clean as possible ideally
<a routerLink="" attributeSelectorForComponent></a>
Issue - Trying to prevent routerLink from firing when [attr.disabled]
is present on the anchor tag, with a click listener.
@HostListener('click', ['$event']) onMouseClick(event: Event) {
event.stopImmediatePropagation();
event.preventDefault()
}
Removed the disabled logic from the equation for simplicity, routerLink is still fired regardless.
Proposed solutions - How can I conditionally disable the routerLink attribute? Doesn't really help address my issue, disabling pointer-events will only disable mouse events not keyboard events, and also prevents me from being able to remove the pointer-events: none with a mouseover, click ect requiring what would be a relatively convoluted solution to detect the disable attribute and remove the css accordingly, and in general seems like more a hacky solution than a correct one.
[routerLink]="null" (and undefined ) is now officially used to disable the routerLink .
Linking Routes in HTMLTo add links to one of the routes, use the routerLink directive in HTML. This directive accepts an array. The first parameter is the name of the route, and the second parameter is the parameters that you want to pass with the route.
In Angular, RouterLink is a directive for navigating to a different route declaratively. Router. navigate and Router. navigateByURL are two methods available to the Router class to navigate imperatively in your component classes. Let's explore how to use RouterLink , Router.
There is no solution that would lead to this markup <a routerLink="" attributeSelectorForComponent></a>
.
The solution you tried won't work because stopImmediatePropagation
is meant to prevent the event from bubbling, and preventDefault
is meant to prevent the default browser behavior for this type of event (e.g: submit event will trigger a POST
request). In either case, Angular will be notified of the event and will react accordingly.
A clean solution would have been possible if the RouterLink
directive had a exportAs
attribute. In that case, it would have been possible to control the RouterLink
from a custom directive. Unfortunately, that is not the case (RouterLink source)
The only option left is to extend the RouterLinkWithHref
directive like this:
@Directive({
selector: "a[myRouterLink],area[myRouterLink]"
})
export class MyDirective extends RouterLinkWithHref implements OnChanges {
@Input()
myRouterLink;
@Input()
myDisabled;
constructor(
private myRouter: Router,
private myRoute: ActivatedRoute,
private myLocationStrategy: LocationStrategy,
private host: ElementRef
) {
super(myRouter, myRoute, myLocationStrategy);
}
ngOnChanges() {
if (this.myDisabled) {
this.host.nativeElement.setAttribute("disabled", "disabled");
this.routerLink = null;
} else {
this.host.nativeElement.removeAttribute("disabled");
this.routerLink = this.myRouterLink;
}
}
}
This gives the following markup: <a myRouterLink="a" [myDisabled]="disabled"></a>
Note that for a full working solution, you would have to also extend RouterLink
You can try the demo here: https://stackblitz.com/edit/angular-p2w4ff
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With