Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exhibits a Windows bias by consistently presenting Windows and PowerShell examples first and exclusively, especially in command-line instructions and project setup. Directory paths, shell commands, and cleanup steps are all shown using Windows conventions (e.g., C:\ paths, PowerShell commands), with no equivalent Linux/macOS shell examples. Package references and environment variable configuration do mention Linux and macOS, but practical usage instructions and examples are Windows-centric. There are no bash/zsh or Linux/macOS terminal examples, and the workflow assumes Visual Studio or Visual Studio Code on Windows.
Recommendations
- Provide equivalent Linux/macOS shell examples (e.g., bash/zsh) alongside PowerShell commands for directory creation, navigation, and cleanup.
- Show Linux/macOS directory paths (e.g., /home/user/msBuildDemo) in addition to Windows paths.
- Include instructions for running MSBuild and dotnet CLI on Linux/macOS, including any platform-specific considerations.
- Demonstrate usage of Azure.Bicep.CommandLine.linux-x64 and osx-x64 in project file examples, not just win-x64.
- Add guidance for installing prerequisites (e.g., .NET SDK, MSBuild) on Linux/macOS, including package manager commands.
- Ensure all code and command examples are presented in platform-agnostic tabs or sections, so users can easily find instructions relevant to their OS.
Create Pull Request