Templates do not have a Frameworks tab on the Package Details page. Should we also disallow/warn users when they try to combine the packageType = template filter with frameworks filters? The behaviors across the frameworks tab and frameworks filters should be consistent.
Q: Are target frameworks expected with template packages? Most template packages in our ecosystem do not have target frameworks, but a handful do.
A: Template packages aren't required to have any particular structure, as they're not recognized by the tooling at all. Some template packages have Target Frameworks because this is needed to build the package.
Target Frameworks have no relevance to the consumer of a template package, so combining the 'Template' package type filter with a Frameworks filter is not useful.
Solution
Should we disallow/warn users when they try to combine the packageType = template filter with frameworks filters?
Problem description
Templates do not have a Frameworks tab on the Package Details page. Should we also disallow/warn users when they try to combine the
packageType = template
filter with frameworks filters? The behaviors across the frameworks tab and frameworks filters should be consistent.Q: Are target frameworks expected with template packages? Most template packages in our ecosystem do not have target frameworks, but a handful do.
A: Template packages aren't required to have any particular structure, as they're not recognized by the tooling at all. Some template packages have Target Frameworks because this is needed to build the package.
Target Frameworks have no relevance to the consumer of a template package, so combining the 'Template' package type filter with a Frameworks filter is not useful.
Solution
Should we disallow/warn users when they try to combine the
packageType = template
filter with frameworks filters?