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. |
||
|---|---|---|
| .vsts-pipelines/builds | ||
| benchmarks/Microsoft.AspNetCore.Razor.Performance | ||
| build | ||
| shared/Microsoft.AspNetCore.Razor.TagHelpers.Testing.Sources | ||
| src | ||
| test | ||
| tooling | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| LICENSE.txt | ||
| NuGet.config | ||
| NuGetPackageVerifier.json | ||
| README.md | ||
| Razor.sln | ||
| build.cmd | ||
| build.sh | ||
| korebuild-lock.txt | ||
| korebuild.json | ||
| run.cmd | ||
| run.ps1 | ||
| run.sh | ||
| version.props | ||
README.md
Razor
Travis: 
The Razor syntax provides a fast, terse, clean and lightweight way to combine server code with HTML to create dynamic web content. This repo contains the parser and the C# code generator for the Razor syntax.
This project is part of ASP.NET Core. You can find samples, documentation and getting started instructions for ASP.NET Core at the Home repo.
Building from source
To run a complete build on command line only, execute build.cmd or build.sh without arguments. See developer documentation for more details.