Skip to content

Commit

Permalink
[Ignore] Update PSScriptAnalyzer issue template (#1585)
Browse files Browse the repository at this point in the history 
Make the PSScriptAnalyzer issue redirect template more explicit about what PSScriptAnalyzer handles in the PowerShell extension.
  • Loading branch information
@rjmholt
rjmholt authored Oct 16, 2018
1 parent 55e8ca3 commit 0388343
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions .github/ISSUE_TEMPLATE/Bug_Report_PSScriptAnalyzer.md
View file
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
---
name: PSScriptAnalyzer bug report 🚦
about: PSScriptAnalyzer bugs are tracked in a separate GitHub repo.
name: Script analysis or formatting bug report 🚦🖌️
about: Script analysis and formatting are provided by PSScriptAnalyzer, whose issues are tracked in a different GitHub repository.

---

* Please submit PSScriptAnalyzer issues to the
* Please submit script analysis and formatting issues to the
[PSScriptAnalyzer](https://github.com/powershell/PSScriptAnalyzer/issues) repo on GitHub.

2 comments on commit 0388343

@codykonior
Copy link

@codykonior codykonior commented on 0388343 Oct 18, 2018 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that this isn't clear.

Code formatting for me works with Invoke-Formatter (provided by PSScriptAnalyzer) but it doesn't work at all when called from the VS Code PowerShell extension.

Are you sure I should raise that with them? What about everyone/anyone else with their issues?

@rjmholt
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a fair point. Naturally if you've identified an issue that only occurs within the extension, that's our issue.

The vast majority of the formatting-related issues we get are ones where the formatting works, but it formats something "wrong" or different to how the user wants. Which is something PSScriptAnalyzer controls rather than us.

I'll change the description, but the longer it gets the less clear it becomes.

Can you also please open an issue to track your bug in https://github.com/PowerShell/vscode-PowerShell

Please sign in to comment.