bafe1b27ff
Addresses a blocking issue for FAR of types when used in user-code in a directive. The FAR infrastructure is skipping over the directive code because it's mapped to `#hidden`. As you can see in the code, the token provided by the user is already included in the projection mappings. I think we didn't do this before because we didn't expect this code to need line numbers - it's not really debuggable, and design-time codegen doesn't happen when you build the project. I think it's OK for now that we don't line-map (or include) directives based on view imports. If you trigger FAR on an `@inject ...` in an import for instance, you'll find the reference for the view import file. That seems pretty good, and the only cases I can really imagine it being broken would be for go-to-definition (within a Razor view). Lets revisit in the future based on feedback. |
||
|---|---|---|
| .. | ||
| DefaultMetadataIdentifierFeatureTest.cs | ||
| DefaultTagHelperOptimizationPassTest.cs | ||
| DefaultTagHelperTargetExtensionTest.cs | ||
| DesignTimeDirectiveTargetExtensionTest.cs | ||
| FunctionsDirectivePassTest.cs | ||
| InheritsDirectivePassTest.cs | ||
| MetadataAttributePassTest.cs | ||
| MetadataAttributeTargetExtensionTest.cs | ||
| PreallocatedAttributeTargetExtensionTest.cs | ||
| SectionDirectivePassTest.cs | ||
| SectionTargetExtensionTest.cs | ||
| TemplateTargetExtensionTest.cs | ||