You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One comment I'd have is that as you start to think about single line objects, consider what would happen if you have a bicep linter and your linter converts from single-line to multi-line.
With single line, these would be the same in bicep:
However, a simple code formatting tool may have issues converting between the two since there's not just a white space change.
The linting tool would have to know that the comma is needed in single-line, but not needed in multi-line.
Give that changing lines involved more than just white-space, my suggestion is that you either support just a white-space separator or support both white-space and comma.
Personally, I support the second syntax (commas) because then each object is a (semi) valid JSON primitive. It would be super nice if it was a valid primitive, but that would require supporting real quote characters :-)
Activity
benc-uk commentedon Nov 5, 2020
Please... especially when LoC and verbosity are some of the advantages of Bicep
By single line assume we mean allowing something like
ChristopherGLewis commentedon Jan 13, 2021
One comment I'd have is that as you start to think about single line objects, consider what would happen if you have a bicep linter and your linter converts from single-line to multi-line.
With single line, these would be the same in bicep:
However, a simple code formatting tool may have issues converting between the two since there's not just a white space change.
The linting tool would have to know that the comma is needed in single-line, but not needed in multi-line.
Give that changing lines involved more than just white-space, my suggestion is that you either support just a white-space separator or support both white-space and comma.
This would mean that this would be valid syntax:
Along with
Personally, I support the second syntax (commas) because then each object is a (semi) valid JSON primitive. It would be super nice if it was a valid primitive, but that would require supporting real quote characters :-)
[-]Support single-line objects arrays[/-][+]Support single-line objects/arrays[/+]dciborow commentedon Aug 27, 2021
An alternative could be simply providing a folding option in VS Code, which also shows the "folded" contents in a csv list.
Here is an example of how PyCharm does this folding docstrings.

MariusStorhaug commentedon Mar 5, 2022
Seems the same applies for the contains() function.
Instead of writing
I would rather be able to write:
ChristopherGLewis commentedon Mar 7, 2022
I get around the
||with another var and a contains:miqm commentedon Jun 20, 2022
Anthony Martin (@anthony-c-martin) - we can probably remove this from the limitation list in Readme.md :)
HenrikSommer-Energinet commentedon Jul 6, 2022
Remember to update documentation: https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/data-types#arrays
anthony-c-martin commentedon Jul 6, 2022
@HenrikSommer-eng, thanks for reminding me - I have raised https://github.com/MicrosoftDocs/azure-docs/issues/95371 for our docs team to pick up.