Skip to content

Conversation

@DustinCampbell
Copy link
Member

@DustinCampbell DustinCampbell commented Jun 16, 2025

Important

This affects the Razor SDK. When the compiler flows to the .NET SDK, this commit will be needed: dotnet/sdk@a9d343d.

Add Parent properties to all of the nested tag helper objects:

  • AllowedChildTagDescriptor.Parent -> TagHelperDescriptor
  • BoundAttributeDescriptor.Parent -> TagHelperDescriptor
  • BoundAttributeParameterDescriptor.Parent -> BoundAttributeDescriptor
  • TagMatchingRuleDescriptor.Parent -> TagHelperDescriptor
  • RequiredAttributeDescriptor.Parent -> TagMatchingRuleDescriptor

This removes the need for BoundAttribute and BoundAttributeParameterDescriptor to duplicate the Kind property from TagHelperDescriptor.

- Add AllowedChildTagDescriptor.Parent -> TagHelperDescriptor
- Add BoundAttributeDescriptor.Parent -> TagHelperDescriptor
- Add BoundAttributeParamterDescriptor.Parent -> BoundAttributeDescriptor
- Add TagMatchingRuleDescriptor.Parent -> TagHelperDescriptor
- Add RequiredAttributeDescriptor.Parent -> TagMatchingRuleDescriptor
- Add nullability annotations
- Use ArgHelper throughout
This can be retrieved via the Parent property.
This can be retrieved via the Parent property
@DustinCampbell DustinCampbell requested review from a team as code owners June 16, 2025 17:29
@DustinCampbell DustinCampbell changed the title Add Parent property to nested tag helper objects Compiler: Add Parent property to nested tag helper objects Jun 16, 2025
Copy link
Member

@davidwengier davidwengier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tooling looks good.

Do you remember if we still need a dual insertion for serialization format changes, for VS Code?

@DustinCampbell
Copy link
Member Author

Do you remember if we still need a dual insertion for serialization format changes, for VS Code?

I don't recall. I was wondering about that too. I don't think we do because we deploy both RZLS and MS.VisualStudioCore.RazorExtension to VS Code at the same time and no longer have an EA from Razor to Roslyn. However, I wasn't deeply involved in that big EA change.

@davidwengier
Copy link
Member

Thats what I think too, but I think is the first test of the theory. Will be easy enough to find out :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants