edae5583cf
#### Details When porting #7046 to other repos, I noticed some style inconsistencies that had crept into our PowerShell scripts. We already recommend the PowerShell extension for vscode. This PR enables its automatic formatting features for PowerShell scripts. I also ran the script against `./tools/get-chrome-web-store-refresh-token.ps1` and `./tools/clearly-defined/check-clearly-defined.ps1` to ensure consistent formatting. The first script was already well formatted--the second received some minor whitespace tweaks. ##### Motivation Code consistency ##### Context <!-- Are there any parts that you've intentionally left out-of-scope for a later PR to handle? --> <!-- Were there any alternative approaches you considered? What tradeoffs did you consider? --> #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [n/a] Addresses an existing issue: - [s] Ran `yarn fastpass` - [n/a] Added/updated relevant unit test(s) (and ran `yarn test`) - [n/a] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [n/a] (UI changes only) Added screenshots/GIFs to description above - [n/a] (UI changes only) Verified usability with NVDA/JAWS |
||
|---|---|---|
| .. | ||
| extensions.json | ||
| launch.json | ||
| settings.json | ||
| tasks.json | ||
| tsc.json | ||