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

API namespace cleanup for tag helpers #578

Closed
Eilon opened this issue Oct 19, 2015 · 5 comments
Closed

API namespace cleanup for tag helpers #578

Eilon opened this issue Oct 19, 2015 · 5 comments
Assignees
Milestone

Comments

@Eilon
Copy link
Member

Eilon commented Oct 19, 2015

From a meeting with @dougbu @rynowak @DamianEdwards

Move what’s in the Microsoft.AspNet.Razor.TagHelpers namespace to something like
Microsoft.AspNet.Razor.Compilation.TagHelpers.

And move what's in the Microsoft.AspNet.Razor.Runtime.TagHelpers namespace to Microsoft.AspNet.Razor.TagHelpers. An alternative that we considered was to rename it to Microsoft.AspNet.Html.TagHelpers, because it's not really Razor-specific, but meh.

@Eilon Eilon added this to the 4.0.0-rc1 milestone Oct 19, 2015
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
- 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
Copy link
Contributor

NTaylorMullen added a commit to aspnet/RazorTooling that referenced this issue Oct 22, 2015
- Updated namespaces.
@dougbu
Copy link
Member

dougbu commented Oct 22, 2015

aspnet/Mvc@0e25470 leaves references to Microsoft.AspNet.Razor.Runtime.TagHelpers in the LinkTagHelper and ScriptTagHelper. Either unused usings were not removed or this issue should be reopened and the dangling type moved to Microsoft.AspNet.Razor.TagHelpers.

Who reviewed that commit BTW? I don't remember a PR for it.

@NTaylorMullen
Copy link
Contributor

It was a reaction. Shouldn't need a review. As for them having Runtime.TagHelpers. That's due to them creating new DefaultTagHelperContents

@dougbu
Copy link
Member

dougbu commented Oct 22, 2015

If they need to do that, others will as well. DefaultTagHelperContent is not in the correct namespace yet.

@dougbu dougbu reopened this Oct 22, 2015
NTaylorMullen added a commit to aspnet/Mvc that referenced this issue Oct 22, 2015
@NTaylorMullen
Copy link
Contributor

Moved DefaultTagHelperContent to Razor.TagHelpers

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants