Unsubscribe from Observables and DOM events. Stop interval timers. Unregister all callbacks that this directive registered with global or application services. You risk memory leaks if you neglect to do so.
Here are the pertinent excerpts from that HeroDetailComponent: src/app/hero-detail.component.ts (template) template:`
<div>
<img src="{{heroImageUrl}}">
<span [style.text-decoration]="lineThrough">
{{prefix}} {{hero?.name}}
</span>
<button (click)="delete()">Delete</button>
</div>` src/app/hero-detail.component.ts (deleteRequest) // This component makes a request but it can't actually delete a hero.
deleteRequest =newEventEmitter<Hero>();delete(){this.deleteRequest.emit(this.hero);}
The component defines a deleteRequest property that returns an EventEmitter. When the user clicks delete, the component invokes the delete() method, telling the EventEmitter to emit a Hero object.
Now imagine a hosting parent component that binds to the HeroDetailComponent's deleteRequest event.
<app-hero-detail (deleteRequest)="deleteHero($event)" [hero]="currentHero"></app-hero-detail> When the deleteRequest event fires, Angular calls the parent component's deleteHero method, passing the hero-to-delete (emitted by HeroDetail) in the $event variable.
Angular offers a special two-way data binding syntax for this purpose, [(x)]. The [(x)] syntax combines the brackets of property binding, [x], with the parentheses of event binding, (x).
The import statement specifies an additional ElementRef symbol from the Angular core library:
You use the ElementRef in the directive's constructor to inject a reference to the host DOM element, the element to which you applied appHighlight.
ElementRef grants direct access to the host DOM element through its nativeElement property.
This first implementation sets the background color of the host element to yellow.
@HostListener The @HostListener decorator lets you subscribe to events of the DOM element that hosts an attribute directive, the <p> in this case.
Of course you could reach into the DOM with standard JavaScript and attach event listeners manually. There are at least three problems with that approach:
1.You have to write the listeners correctly.
2.The code must detach the listener when the directive is destroyed to avoid memory leaks.
3.Talking to DOM API directly isn't a best practice.
SDLC - Software Development Life Cycle is a process used by the software industry to design, develop and test high quality softwares. 1- Requirement Analysis 2- Defining Requirements To clearly define and document the product requirements SRS (Software Requirement Specification) document which consists of all the product requirements to be designed and developed during the project life cycle. 3- Designing the Product Architecture One design approach for the product architecture is proposed and documented in a DDS - Design Document Specification . DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product. DDS defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules. 4- Developing the ...
if we overuse it might make our code too complex and hard to read. The most useful feature of Compass are; sprites , vertical rhytm, horiznal lists, creating vendor prefixes. However it is still better idea to use Autoprefixer over mixins for creating vendor prefixes. Why? Because Autoprefixes is a process that is gonna work even if you do not use compass/sass. You do not need to learn a new code. You also can keep having tips in your IDE when you want to change something. Autoprefixer is a PostCSS plugin which parse your CSS and add vendor prefixes. Href : https://autoprefixer.github.io/ https://fatihhayrioglu.com/browserlist-ve-autoprefixere-guncelleme/