-
Notifications
You must be signed in to change notification settings - Fork 763
Issues: Azure/bicep
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Module Good for newcomers
Quality Sprint: Yes
name
property is missing intellisense description and length constraint
good first issue
#15502
opened Nov 5, 2024 by
asilverman
ms-azuretools.vscode-bicep Generate Parameters File to json not exporting default parameters
bug
Something isn't working
good first issue
Good for newcomers
Quality Sprint: Yes
Variable count linter should be disabled for "library" modules
good first issue
Good for newcomers
Needs: Upvote
This issue requires more votes to be considered
story: linter rules
#15456
opened Nov 1, 2024 by
jeskew
Better error message for unsupported YAML file syntax
enhancement
New feature or request
good first issue
Good for newcomers
Quality Sprint: Yes
Improve compile-time validation of the resourceId() function for hard-coded resource types.
enhancement
New feature or request
good first issue
Good for newcomers
Needs: Upvote
This issue requires more votes to be considered
Support tagged unions in type property access
design approved
The team has reviewed and signed off on this design
enhancement
New feature or request
good first issue
Good for newcomers
Needs: Upvote
This issue requires more votes to be considered
type system
Display Parameter Default Value in Completions
enhancement
New feature or request
good first issue
Good for newcomers
Warning about missing resource types should be more explicit about impact (and where is the link to the help page?)
good first issue
Good for newcomers
Needs: Upvote
This issue requires more votes to be considered
Improve loop code generation when using a complex expression as loop source
enhancement
New feature or request
good first issue
Good for newcomers
Deployment Pane: initial dropdown value not picked up
bug
Something isn't working
good first issue
Good for newcomers
Quality sprint: No
story: deploy pane
Quick fix for adding parameter/variable for missing variable
enhancement
New feature or request
good first issue
Good for newcomers
Missing part of control+space completion for module in VS Code
enhancement
New feature or request
good first issue
Good for newcomers
Linter rule to detect referencing of child resources using New feature or request
good first issue
Good for newcomers
story: linter rules
resourceId()
function
enhancement
Warn on unused imports
enhancement
New feature or request
good first issue
Good for newcomers
story: linter rules
Warn on unused type declarations
enhancement
New feature or request
good first issue
Good for newcomers
story: linter rules
auto-fix: grouped auto fixes like Remove all unused parameters
enhancement
New feature or request
good first issue
Good for newcomers
Typing commit character ":" when a resource completion is selected while typing out a ternary expression will output "resource:" instead of just ":"
bug
Something isn't working
good first issue
Good for newcomers
Indexing arrays from the end
design approved
The team has reviewed and signed off on this design
enhancement
New feature or request
good first issue
Good for newcomers
proposal
"View Type Documentation" link in VS Code should link to api version-specific page
bug
Something isn't working
good first issue
Good for newcomers
Dedicated function for parsing resource IDs
enhancement
New feature or request
good first issue
Good for newcomers
[LinterRuleIdea] Rule to enforce description on parameters
enhancement
New feature or request
good first issue
Good for newcomers
story: linter rules
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.