Angular - DirectivesWhy is it important that directives in Angular follow a clear selector naming convention like prefixing with 'app'?ATo automatically generate documentationBTo make directives load faster in the browserCTo avoid conflicts with standard HTML elements and other librariesDTo ensure directives are only used in root modulesCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand naming conventions purposePrefixing selectors prevents name clashes with native HTML or third-party libraries.Step 2: Evaluate options for naming benefitsOnly avoiding conflicts matches the reason for prefixing selectors.Final Answer:To avoid conflicts with standard HTML elements and other libraries -> Option CQuick Check:Selector prefixing prevents conflicts [OK]Quick Trick: Prefix selectors to avoid naming conflicts [OK]Common Mistakes:Thinking prefix improves performanceBelieving prefix restricts module usageAssuming prefix auto-generates docs
Master "Directives" in Angular9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallPerf
More Angular Quizzes Angular Fundamentals - Angular project structure walkthrough - Quiz 14medium Component Interaction - @ContentChild and content projection - Quiz 6medium Components - Creating components with CLI - Quiz 5medium Directives - Structural vs attribute directives - Quiz 8hard Directives - *ngIf for conditional rendering - Quiz 6medium Directives - *ngFor for list rendering - Quiz 15hard Directives - Structural vs attribute directives - Quiz 7medium Templates and Data Binding - Template expressions and statements - Quiz 12easy Templates and Data Binding - Two-way binding with ngModel - Quiz 4medium TypeScript in Angular - Enums in Angular applications - Quiz 13medium