3b53f04518
- This moves ParserContext closer to operating on a RazorSourceDocument and exposes it at the parsing layer. - Was not able to replace the `ITextDocument` property on `ParserContext` due to its current wiring. Our tokenizers rely on a single reader that iterates over the document and take turns tokenizing characters from that reader. The reader that the tokenizers pull from is also highly coupled with the parsers implementations; they end up moving the readers pointer frequently. |
||
|---|---|---|
| .. | ||
| Microsoft.AspNetCore.Mvc.Razor.Extensions.Test | ||
| Microsoft.AspNetCore.Razor.Language.Test | ||
| Microsoft.AspNetCore.Razor.Performance | ||
| Microsoft.AspNetCore.Razor.Runtime.Test | ||
| Microsoft.AspNetCore.Razor.Test.Common | ||
| Microsoft.AspNetCore.Razor.Test.MvcShim | ||
| Microsoft.CodeAnalysis.Razor.Test | ||
| Microsoft.VisualStudio.LanguageServices.Razor.Test | ||
| RazorPageGenerator.Test | ||