📄 JS API 1/4: Screen recording

#js #MediaRecorder

⚠️ Non-refactored

✅ Link: https://javascript.plainenglish.io/18-powerful-javascript-skills-for-senior-engineers-17c51990997e

📄 JS API 2/4: Page visibility

#js #visibilityChange

⚠️ Non-refactored

✅ Link: https://javascript.plainenglish.io/18-powerful-javascript-skills-for-senior-engineers-17c51990997e

📄 JS API 3/4: IntersectionObserver

#js #IntersectionObserver

⚠️ Non-refactored

✅ Link: https://javascript.plainenglish.io/18-powerful-javascript-skills-for-senior-engineers-17c51990997e

📄 JS API 4/4: MutationObserver

#js #MutationObserver

⚠️ Non-refactored

✅ Link: https://javascript.plainenglish.io/18-powerful-javascript-skills-for-senior-engineers-17c51990997e

📄 Angular Resolver Use Case

#angular #resolver

🚩> Angular 16

✅ Article Link:
https://itnext.io/understanding-angular-resolvers-b49f6c227278

📄 @Attribute Decorator in Angular

#angular #decorator #attribute

As you can see, when we trigger the change detection by emitting the click event, Angular is checking the value.
We can be more efficient in this case if we use the @Attribute decorator. With this change, Angular will evaluate it once and forget about it. As a general rule, I prefer the @Attribute() approach when the string is a fixed value that never changes.

import { Component, Attribute } from '@angular/core';

@Component({...})
export class ButtonComponent {

  constructor(
    @Attribute('type') 
    public type: ButtonType = 'primary'
  ) {
  }

}

✅ Article Link: https://netbasal.com/getting-to-know-the-attribute-decorator-in-angular-4f7c9fb61243