We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I click right-click on a "problem" and then select "Show documentation for:" I expect it to take me to the documentation.
Instead it takes me to a dead link.
Example: https://github.com/PowerShell/PSScriptAnalyzer/blob/master/RuleDocumentation/AvoidUsingWriteHost.md
Name Value ---- ----- PSVersion 5.1.14409.1018 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.14409.1018 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1
1.61.0 ee8c7def80afc00dd6e593ef12f37756d8f504ea x64
[email protected]
No response
The text was updated successfully, but these errors were encountered:
The location got changed upstream, @bgold09 fixed it, I'll get a new release out ASAP.
Sorry, something went wrong.
Hot-fix release published with the fix for this!
Successfully merging a pull request may close this issue.
Prerequisites
Summary
When I click right-click on a "problem" and then select "Show documentation for:" I expect it to take me to the documentation.
Instead it takes me to a dead link.
Example: https://github.com/PowerShell/PSScriptAnalyzer/blob/master/RuleDocumentation/AvoidUsingWriteHost.md
PowerShell Version
Visual Studio Code Version
Extension Version
[email protected]
Steps to Reproduce
When I click right-click on a "problem" and then select "Show documentation for:" I expect it to take me to the documentation.
Instead it takes me to a dead link.
Example: https://github.com/PowerShell/PSScriptAnalyzer/blob/master/RuleDocumentation/AvoidUsingWriteHost.md
Visuals
No response
Logs
No response
The text was updated successfully, but these errors were encountered: