Follow-up to cleaning up obsolete types in Razor #28706
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #27529.
This PR is a follow-up to #28418. Removing all the references to RazorEngine ended up being a fair significant chunk of work so I've pulled it out of this for now.
This PR covers the things discussed during the API review:
GetItem
interface per @NTaylorMullen's recommendation here.IRazorEngineBuilder
in directives in V1_x and V2_x.IRazorEngineBuilder
extensions.RazorEngine
. The cost of removing all the references in the V1_x and V2_x projects and in the types in favor of RazorProjectEngine turned out to be pretty high so I opted not to do this. Tracking this here in case we want to invest time in this.