This repository was archived by the owner on Dec 19, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 223
Create LineMappings for 0 length spans to ensure IntelliSense is provided when typing @ #1155
Comments
NTaylorMullen
added a commit
that referenced
this issue
Apr 3, 2017
- At design time we weren't generating line mappings when a user would type `@` or `@(`. This results in no C# IntelliSense being provided to the user because the editor hasn't mapped any of Razor to the C# buffer. - Updated the design time renderer and design time writer to account for empty expressions. - Modified the `DefaultIRLoweringPhase` to set source locations on empty expression nodes. - Re-generated test files to account for 0 length line mappings on empty expression nodes. #1155
NTaylorMullen
added a commit
that referenced
this issue
Apr 3, 2017
- At design time we weren't generating line mappings when a user would type `@` or `@(`. This results in no C# IntelliSense being provided to the user because the editor hasn't mapped any of Razor to the C# buffer. - Updated the design time renderer and design time writer to account for empty expressions. - Modified the `DefaultIRLoweringPhase` to set source locations on empty expression nodes. - Re-generated test files to account for 0 length line mappings on empty expression nodes. #1155
NTaylorMullen
added a commit
that referenced
this issue
Apr 3, 2017
- At design time we weren't generating line mappings when a user would type `@` or `@(`. This results in no C# IntelliSense being provided to the user because the editor hasn't mapped any of Razor to the C# buffer. - Updated the design time renderer and design time writer to account for empty expressions. - Modified the `DefaultIRLoweringPhase` to set source locations on empty expression nodes. - Re-generated test files to account for 0 length line mappings on empty expression nodes. #1155
NTaylorMullen
added a commit
that referenced
this issue
Apr 3, 2017
- At design time we weren't generating line mappings when a user would type `@` or `@(`. This results in no C# IntelliSense being provided to the user because the editor hasn't mapped any of Razor to the C# buffer. - Updated the design time renderer and design time writer to account for empty expressions. - Modified the `DefaultIRLoweringPhase` to set source locations on empty expression nodes. - Re-generated test files to account for 0 length line mappings on empty expression nodes. #1155
NTaylorMullen
added a commit
that referenced
this issue
Apr 3, 2017
- At design time we weren't generating line mappings when a user would type `@` or `@(`. This results in no C# IntelliSense being provided to the user because the editor hasn't mapped any of Razor to the C# buffer. - Modified the `DefaultIRLoweringPhase` to allow for marker symbols, these symbols . - Re-generated test files to account for 0 length line mappings on empty expression nodes. #1155
NTaylorMullen
added a commit
that referenced
this issue
Apr 3, 2017
- At design time we weren't generating line mappings when a user would type `@` or `@(`. This results in no C# IntelliSense being provided to the user because the editor hasn't mapped any of Razor to the C# buffer. - Modified the `DefaultIRLoweringPhase` to allow for marker symbols, these symbols . - Re-generated test files to account for 0 length line mappings on empty expression nodes. #1155
I'm glad that you fixed this to unblock the tooling experience. The way that this works today is largely an artifact of the current design. I have some ideas about this, we might want to take a harder look at |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We no longer generate line mappings for 0 length spans but at design time we must. It enables a user typing the at symbol by itself and getting IntelliSense.
The text was updated successfully, but these errors were encountered: