Merge pull request #701 from fortran-lang/gnikit/issue700

bug: activation fails silently on Windows

Author: gnikit

CHANGELOG.md

@@ -70,6 +70,8 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 
 ### Fixed
 
+- Fixed activation bug on Windows causing the persistent cache to fail
+  ([#700](https://github.com/fortran-lang/vscode-fortran-support/issues/700))
 - Fixed bug where the linter's internal cache directory would not always exist
   ([#698](https://github.com/fortran-lang/vscode-fortran-support/issues/698))
 - Fixed bugs in relative path resolution for `fortls`

src/extension.ts

@@ -48,7 +48,7 @@ export async function activate(context: vscode.ExtensionContext) {
   );
   // Linter is always activated but will only lint if compiler !== Disabled
   const linterCache = path.join(context.storageUri.fsPath, 'include');
-  await vscode.workspace.fs.createDirectory(vscode.Uri.parse(linterCache));
+  await vscode.workspace.fs.createDirectory(vscode.Uri.file(linterCache));
   const linter = new FortranLintingProvider(logger, linterCache);
   context.subscriptions.push(...(await linter.activate()));
   vscode.languages.registerCodeActionsProvider(FortranDocumentSelector(), linter);