5bda62c51d
When an input name is part of the directive selector, it would be good to return the directive as well when performing 'go to definition' or 'go to type definition'. As an example, this would allow 'go to type definition' for ngIf to take the user to the NgIf directive. 'Go to type definition' would otherwise return no results because the input is a generic type. This would also be the case for all primitive input types. PR Close #39243
33 lines
897 B
TypeScript
33 lines
897 B
TypeScript
/**
|
|
* @license
|
|
* Copyright Google LLC All Rights Reserved.
|
|
*
|
|
* Use of this source code is governed by an MIT-style license that can be
|
|
* found in the LICENSE file at https://angular.io/license
|
|
*/
|
|
|
|
import {CommonModule} from '@angular/common';
|
|
import {NgModule} from '@angular/core';
|
|
import {FormsModule} from '@angular/forms';
|
|
import {AppComponent} from './app.component';
|
|
import * as ParsingCases from './parsing-cases';
|
|
|
|
@NgModule({
|
|
imports: [CommonModule, FormsModule],
|
|
declarations: [
|
|
AppComponent,
|
|
ParsingCases.CounterDirective,
|
|
ParsingCases.HintModel,
|
|
ParsingCases.NumberModel,
|
|
ParsingCases.StringModel,
|
|
ParsingCases.TemplateReference,
|
|
ParsingCases.TestComponent,
|
|
ParsingCases.TestPipe,
|
|
ParsingCases.WithContextDirective,
|
|
ParsingCases.CompoundCustomButtonDirective,
|
|
ParsingCases.EventSelectorDirective,
|
|
]
|
|
})
|
|
export class AppModule {
|
|
}
|