Bias Analysis
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias, primarily through the use of Windows-style file paths (e.g., c:\jsontemplates) in all command examples, even when the commands are cross-platform. Linux/macOS equivalents (e.g., /home/user/jsontemplates) are not provided alongside Windows examples. Windows paths are shown first and exclusively in most cases. The install, upgrade, and list-versions commands are only available via Azure CLI, which is cross-platform, but the documentation does not clarify OS-specific installation steps or nuances. The cache location section does mention Linux and Mac paths, but only after Windows. No PowerShell-specific commands are present, but Windows conventions dominate the examples.
Recommendations
- Provide Linux/macOS path examples (e.g., /home/user/jsontemplates) alongside Windows paths in all CLI command samples.
- Explicitly state that file paths should be adapted to the user's OS, and provide a note or table mapping Windows and Linux/macOS conventions.
- When listing cache locations or file system paths, present all OSes equally, or use a tabbed format for each OS.
- Clarify any OS-specific installation or usage differences, especially for commands only available via Azure CLI.
- Avoid using Windows paths as the default in mixed-OS documentation.
Create Pull Request