microsoftgraph / microsoftgraph/msgraph-tools-migration
Use `Write-Debug` instead of `Write-Host` to avoid polluting the output stream
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
if ($Result.Count -gt 0) {
Write-Host -ForegroundColor Green "--------- Your script(s) contains commands that need to conform to the naming convention as per the 'New' column on the table below ---------"
Write-Output $Result | Format-Table
}
if($WriteToFile){
Write-Host -ForegroundColor Blue "Your updated script is on this path: $UpdatedFile"
}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in Microsoft.Graph.Migration.Tool.psm1 at the referenced lines around 143-147 and review how the two Write-Host calls affect the output stream. Replace the diagnostic messages as requested, then verify that command output contains only the intended results while the messages remain available through the debug stream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100