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
Describe the bug
There is a difference of how Markdown is visualized/interpreted in user defined types bicep template and bicep parameters files. In the latter the visualization is not correct.
To Reproduce
Example:
main.bicep
typefooType = {
@description('''Description # Title1 Some text ## Title 2 Some text: ```sql AzureMetrics | where ResourceProvider == 'MICROSOFT.ANALYSISSERVICES' ``` Some text * Bullet1 * Bullet2 Some text ## Title 3 ```json { "key": "value", "key2": "value2", "key3": 1 } ``` ''')
foo1: string?
@description('''Description ```sql AzureMetrics | where ResourceProvider == 'MICROSOFT.ANALYSISSERVICES' ``` ''')
foo2: string?
}
paramfoofooType = {}
parameters.bicepparam. Note using needs to point to container registry
using''paramfoo = {
}
The visualization of the descriptions in .bicep file:
Visualization of the descriptions in .bicepparam file:
Note that the issue appears if you point using to container registry. If you reference local .bicep file visualization is ok.
I believe this is not the first time this happens so may you can somehow use the same code or sync those two functions that do those things in order to avoid differences in those and having to report them when it happens.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Bicep version
Bicep CLI version 0.29.47 (132ade5)
Describe the bug
There is a difference of how Markdown is visualized/interpreted in user defined types bicep template and bicep parameters files. In the latter the visualization is not correct.
To Reproduce
Example:
main.bicep
parameters.bicepparam. Note using needs to point to container registry
The visualization of the descriptions in .bicep file:
Visualization of the descriptions in .bicepparam file:
Note that the issue appears if you point using to container registry. If you reference local .bicep file visualization is ok.
I believe this is not the first time this happens so may you can somehow use the same code or sync those two functions that do those things in order to avoid differences in those and having to report them when it happens.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: