Mikolaj Mackowiak

> > This approach may not be viable when crossing scope boundaries with modules, as 'scope escaping' with resources is not currently supported and has some hard challenges around auditability....

> The nice thing about the anonymous module suggestion is could allow scoped parameters, but I'm not sure how this would be handled in the resultant ARM template. I think...

> I just added a related issue suggesting a kind of inline module synax: #4555 > > To me one of the benefits of having a compiler that front-ends ARM...

This error occurred on MacOS. I tried to reproduce it on Windows and I couldn't :/

Also, after looking into code it doesn't seem to be a bug in Bicep. probably we did receive some odd values from VSCode. Perhaps we should wrap Handlers with try-catch...

Ugh, I wrote that when if's weren't yet implemented... Question is now how to mitigate it. My proposal is to warn (or even just notify?) and not throw error when...

ok, I'll handle this shortly, assign this to me please.

> > > On the other hand, supporting if...elseif...elseif....elseif..........else would allow the user to express their intent regardless of us detecting the expressions are mutually exclusive. switch perhaps?

Hmm, we've a problem... I implemented warning but when I tried to deploy generated template: ``` param createMode string { default: 'v1' allowed: [ 'v1' 'v2' ] } resource vnet1...

For the record, implementation of warning on conditional is on my fork: https://github.com/miqm/bicep/tree/bugfix/duplicate-names-with-conditions-1410 for future pickup.