_output() writes directly via Path.write_text(). If the target path is unwritable / parent dir missing / path is a directory, this will raise an OSError that won't be caught by the Typer interface (which only catches UsethisError), likely resulting in a traceback. Consider catching OSError here (or in the interface) and re-raising a UsethisError with a clear message that includes the output path.

This doc update implies --output-file is only supported for usethis show sonarqube, but the PR adds it to all usethis show subcommands (backend, name, sonarqube). The reference should either document --output-file as a shared usethis show option or list it under each usethis show <subcommand> that supports it, to avoid misleading users.

This test is described as simulating the shell redirect issue, but pre-creating an empty sonar-project.properties file makes get_sonar_project_properties() return that empty file by design. That means the test doesn't actually validate that --output-file avoids the redirect problem (i.e., writing after generation when the file did not exist at generation time), and the current assertion (content != "") can pass even if the command only writes a newline. Consider removing this test or rewriting it to cover the intended scenario (e.g., ensure the output file does not exist before invocation and assert the written file contains expected generated properties).

The --output-file option is documented as writing output to a file instead of stdout, but this test only asserts the file contents. Adding an assertion that result.output is empty (and doing the same for the other test_output_file cases in this file) would better lock in the intended behavior and prevent accidental future regressions that write to both stdout and the file.