Azure / Azure/bicep

Auto-fix/refactoring idea: use safe deference and coalesce instead of contains and ternary operator

Open
#10,491 2 comments 2 reactions 0 assignees View on GitHub
devdiv
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

e.g. from @brwilkinson

> I have a long list of global variable overrides in every Module ... so much easier to read...

![image](https://user-images.githubusercontent.com/6913354/233700171-7c2d0979-6287-483c-bc14-33fed7623a92.png)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the issue’s example and screenshot, then inspect how Bicep currently represents or diagnoses `contains` expressions and ternary operators. The issue names no files, tests, or entry points; done would require an agreed refactoring scope plus implementation and tests for the proposed auto-fix.

Written by the indexing model from the issue text.

Assessment

Domain
compilers, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.