This repository has been archived by the owner on Dec 19, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 224
API namespace cleanup for tag helpers #578
Comments
NTaylorMullen
added a commit
that referenced
this issue
Oct 20, 2015
- Name changed to `Microsoft.AspNet.Razor.Compilation.TagHelpers`. - Changed folder locations to reflect namespace change. #578
NTaylorMullen
added a commit
that referenced
this issue
Oct 20, 2015
- Changed name to `Microsoft.AspNet.Razor.TagHelpers`. - Updated folder structure to reflect new namespaces. - Updated generated code files to reflect new runtime type namespaces. #578
Merged
NTaylorMullen
added a commit
that referenced
this issue
Oct 20, 2015
…r.TagHelpers`. - Required adding a new using statement to generated code. Regened output files. - Fixed broken documentation. #578
NTaylorMullen
added a commit
that referenced
this issue
Oct 20, 2015
- Name changed to `Microsoft.AspNet.Razor.Compilation.TagHelpers`. - Changed folder locations to reflect namespace change. #578
NTaylorMullen
added a commit
that referenced
this issue
Oct 20, 2015
- Changed name to `Microsoft.AspNet.Razor.TagHelpers`. - Updated folder structure to reflect new namespaces. - Updated generated code files to reflect new runtime type namespaces. #578
NTaylorMullen
added a commit
that referenced
this issue
Oct 20, 2015
…r.TagHelpers`. - Required adding a new using statement to generated code. Regened output files. - Fixed broken documentation. #578
NTaylorMullen
added a commit
that referenced
this issue
Oct 20, 2015
- Disable `TagHelper` infrastructure using statements during design time. - Regenerated code files. #578
NTaylorMullen
added a commit
that referenced
this issue
Oct 21, 2015
- Name changed to `Microsoft.AspNet.Razor.Compilation.TagHelpers`. - Changed folder locations to reflect namespace change. #578
NTaylorMullen
added a commit
that referenced
this issue
Oct 21, 2015
- Changed non-ser facing type names to `Microsoft.AspNet.Razor.TagHelpers`. - Updated folder structure to reflect new namespaces. - Updated generated code files to reflect new runtime type namespaces. #578
NTaylorMullen
added a commit
that referenced
this issue
Oct 21, 2015
- Changed non-user facing type names to `Microsoft.AspNet.Razor.TagHelpers`. - Updated folder structure to reflect new namespaces. - Updated generated code files to reflect new runtime type namespaces. #578
NTaylorMullen
added a commit
that referenced
this issue
Oct 22, 2015
- Name changed to `Microsoft.AspNet.Razor.Compilation.TagHelpers`. - Changed folder locations to reflect namespace change. #578
NTaylorMullen
added a commit
that referenced
this issue
Oct 22, 2015
- Changed non-user facing type names to `Microsoft.AspNet.Razor.TagHelpers`. - Updated folder structure to reflect new namespaces. - Updated generated code files to reflect new runtime type namespaces. #578
NTaylorMullen
added a commit
to aspnet/Mvc
that referenced
this issue
Oct 22, 2015
NTaylorMullen
added a commit
to aspnet/RazorTooling
that referenced
this issue
Oct 22, 2015
- Updated namespaces.
aspnet/Mvc@0e25470 leaves references to Who reviewed that commit BTW? I don't remember a PR for it. |
It was a reaction. Shouldn't need a review. As for them having |
If they need to do that, others will as well. |
NTaylorMullen
added a commit
to aspnet/Mvc
that referenced
this issue
Oct 22, 2015
Moved |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From a meeting with @dougbu @rynowak @DamianEdwards
Move what’s in the
Microsoft.AspNet.Razor.TagHelpers
namespace to something likeMicrosoft.AspNet.Razor.Compilation.TagHelpers
.And move what's in the
Microsoft.AspNet.Razor.Runtime.TagHelpers
namespace toMicrosoft.AspNet.Razor.TagHelpers
. An alternative that we considered was to rename it toMicrosoft.AspNet.Html.TagHelpers
, because it's not really Razor-specific, but meh.The text was updated successfully, but these errors were encountered: