Marcin Jastrzebski

Decompiler should not generate symbolic names with "Name" suffix

1

**Is your feature request related to a problem? Please describe.** The decompiler often generates resource symbolic name with the Name suffix which causes the actual variables holding the resource name...

Remove the `name` property from module references

9

I'm adding this so we can prioritize the fix. This is related to #3355, but I'm hoping there's a fix we can do without additional runtime changes.

**Bicep version** Any **Describe the bug** `targetScope` is an element of the document that should be present in the outline. **To Reproduce** ```bicep targetScope = 'managementGroup' param test string ```...

Add extra logging to msbuild e2e test that is failing in ADO

2

###### Microsoft Reviewers: [Open in CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com/Azure/bicep/pull/13543)

Set or skip an object property based on a condition

87

**Is your feature request related to a problem? Please describe.** When conditionally enabling ipv6 in a template, there are cases where some properties need to be either set or omitted...

In deployments runtime, do not check properties of resources with a `false` condition

28

**Bicep version** `v0.3.255` **Describe the bug** In certain cases, we generate invalid reference() calls in the JSON. **To Reproduce** 1. Start with this bicep file: ```bicep resource one 'Microsoft.Storage/storageAccounts@2019-06-01' =...

**Bicep version** Latest official **Describe the bug** Types are not highlighted in a different color **To Reproduce** **Additional context** Add any other context about the problem here.