Skip to content
This repository has been archived by the owner on Dec 19, 2018. It is now read-only.

TagHelperElementCompletionService does not return TagHelper completions with a prefix. #1224

Closed
NTaylorMullen opened this issue Apr 14, 2017 · 1 comment

Comments

@NTaylorMullen
Copy link
Member

No description provided.

@NTaylorMullen NTaylorMullen added this to the 2.0.0-preview1 milestone Apr 14, 2017
@NTaylorMullen NTaylorMullen self-assigned this Apr 14, 2017
NTaylorMullen added a commit that referenced this issue Apr 14, 2017
- We don't want tooling applying tag helper prefix to what we deem `TagHelper`s. Ultimately we should consume all the necessary data and do that work.
- Added two tests to validate that we're applying tag helper prefix to `TagHelper` element completions for catch-all's and non-catch-alls.

#1224
NTaylorMullen added a commit that referenced this issue Apr 14, 2017
- We don't want tooling applying tag helper prefix to what we deem `TagHelper`s. Ultimately we should consume all the necessary data and do that work.
- Added two tests to validate that we're applying tag helper prefix to `TagHelper` element completions for catch-all's and non-catch-alls.

#1224
NTaylorMullen added a commit that referenced this issue Apr 14, 2017
- We don't want tooling applying tag helper prefix to what we deem `TagHelper`s. Ultimately we should consume all the necessary data and do that work.
- Added two tests to validate that we're applying tag helper prefix to `TagHelper` element completions for catch-all's and non-catch-alls.

#1224
@NTaylorMullen
Copy link
Member Author

cf44f10

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Development

No branches or pull requests

1 participant