fix #50008 by bumping precedence so the 10 template is treated as the primary #50154
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…as the primary when present
There was a problem hiding this comment.
Pull Request Overview
This PR fixes issue #50008 by increasing the precedence value of the Solution template from 100 to 101, ensuring it is treated as the primary template when multiple templates with the same group identity exist.
- Bumped template precedence from 100 to 101 for the Solution template
github-actions
bot
added
the
Area-Common templates
dsplaisted
approved these changes
Aug 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #50008
Templates are parsed from all configured providers, and then grouped by 'groupIdentity' into TemplateGroups.
When a template is instantiated, the TemplateGroup is chosen based on the identity of the template provided by the user in the command, and then the Templates in the TemplateGroup are ordered by Precedence and the maximum one is chosen for parsing all of the rest of the arguments to the template.
In general, the problem in #50008 doesn't happen with the 'core' project templates because we bump the template precedence each release. We haven't done this with the
itemtemplates because they generally haven't changed much and it's not been part of our muscle memory. We should make this a thing in the future for any template changes - in fact we should probably just keep item template precedence in line with the project template precedence.