-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
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
Linter for powershell syntax errors #2413
Conversation
zigford
commented
Apr 4, 2019
- Moved the RunPowershell function out of the psscriptanalyzer into autoload/ale/powershell.vim so that it can be used by other powershell things.
- Added powershell linter which uses powershell itself to parse a script and output any syntax errors
- Added documentation
- Added tests.
I think I'm failing because of the custom linting rules and those rules are conflicting with each other with how the code is currently factored. Should I refactor for the linting rules? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I explained what the linter is saying here.
Apologies for causing all these build failures. So that I don't cause any more in future PR's, could you explain again what is going wrong now? |
The remaining issue is that the Vim help file's list of supported tools needs to match the Markdown list. |
Cheers! 🍻 |