d273c6cd4c
- Prior to this if you had a `TagHelper` whos output hint was not in the final form of the completions we'd fall through into a schema check which resulted in a completion being added when it shouldn't. Example: `TagHelper` for `my-tr` that has an output hint of `tr` would end up getting added to the completion list under `body` because `my-tr` was not in the schema and would then be treated like the `environment` `TagHelper` (a new element). - Added a test to validate that `TagHelper`s with output hints are cross referenced vs. existing completions and do not fall through to a schema check. #1225 |
||
|---|---|---|
| .. | ||
| DefaultTagHelperCompletionServiceTest.cs | ||
| DefaultTagHelperFactsServiceTest.cs | ||
| Microsoft.VisualStudio.LanguageServices.Razor.Test.csproj | ||
| TagHelperDescriptorSerializationTest.cs | ||
| xunit.runner.json | ||