Support 'isHidden' / 'isEnabled' for defined template.json properties

[vlada-shubina]

Now isHidden is only available in host.json, and it leads to perf impact as we need to read host.json files for all templates to see if they are hidden or not. Suggestion is to move this property to template.json and allow to configure for different hosts similar to: #3340

It should be possible to hidden the template or specific its features: symbols (parameters), choices, post actions, primary outputs.

Consider supporting the following notations: <host ID><delimiter>isEnabled
Example:

vs_isEnabled: "true" - template is enabled in VS

my-parameter:
{
     vs_isEnabled: "false", - parameter is disabled in VS
     .... 
}

The logic, including fallback should be evaluated in Edge:

• if template is disabled for specific host, it should not be returned in template list
• if certain feature is disabled for specific host, it should not be returned via API
• if host specific value is not available - use default value (without the prefix)

[DavidKarlas]

For the record, I'm not fan of this, parsing host.json files is not problem anymore afaik since #3292

[DavidKarlas]

Since perf is not major problem anymore, and this should be handled via Constraints, I vote for closing this issue.

[vlada-shubina]

Since perf is not major problem anymore, and this should be handled via Constraints, I vote for closing this issue.

Let's discuss it first before closing. I'm not clear how constraints can be used to hide certain parameters, post actions etc, though it is definitely a solution for hiding whole template.

[DavidKarlas]

I missed that part of issue, I thought its only about current isHidden from host.json file which only allows hiding whole template, not parts of template.