-
Notifications
You must be signed in to change notification settings - Fork 235
Update to PSScriptAnalyzer 1.4.0 #127
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
Comments
I'll talk to Raghu and see if he thinks it might come out on Monday. I'd prefer not to slip the release date since I foolishly announced it already ;) On the other hand, I don't know when VS Code folks plan to release 0.10.7 so the date may need to be slipped anyway. |
I talked to Raghu earlier, he thinks it may take a week before the fix is done, fully tested, and released. Since that's the case, I'll ship 0.4.0 with 1.3.0 and then release an intermediate 0.4.1 release when 1.3.1 comes out. |
How's the PSScriptAnalyzer update coming along? I guess we have the bigger issue of broken diagnostics to fix first, eh? |
I figured out the problem with that, have a PR on the way. They made a behavior-breaking change hidden behind an optional function parameter. I'm adding a unit test to catch future breaks, almost done. I think their next release will drop in the next couple of days so we should be ready to release a new version around the same time. |
Resaved this file as UTF8 and tweaked...
Looks like the good folks on PSScriptAnalyzer are going to try to address as much of the "editor extent" issue as they can. We might get a 1.3.1 drop early next week. It would probably be worth waiting on that drop for 0.4.0.
The text was updated successfully, but these errors were encountered: