Fix New-BTAudio help after custom audio removal - #297
Open
PNHD wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
remove stale New-BTAudio help that says custom audio file paths are supported
document the supported Microsoft notification URI behavior instead
replace the custom-file example with the built-in looping Alarm2 example
keep the Markdown help and comment-based help in sync
Custom audio file paths were deprecated in BurntToast 0.8.1 and removed in 1.0.0, but the current New-BTAudio help still documents them as supported.
Fixes #272
Scope
Documentation only. No executable PowerShell logic or tests are changed.