Minor release - version 2.2.0

### Check List
- Highlight
- [x] `select` keyword - *Merge #165 to fix #149*
- [x] `rank` keyword -  *Merge #165*
- [x] `forall` keyword - *Merge #170 to fix #169*
- Symbol List
- [x] Symbols bug in VSCode +1.40 - *Merge #161 to fix #154*
- [x] Symbols classification - *Merge #141 to fix #140*
- [x] Long named symbols - *Merge #151*
- Settings
- [x] Add more options - *Merge #152*
- Dependencies
- [x] Merge `dependabot` PR's
    - [x] lodash - *Merge #144*
    - [x] mixin-deep - *Merge #146*
    - [x] handlebars - *Merge #155* 
- Code Completion
- [x] Array constructor - *Fix #148*
- New Features
- [x] Breakpoints - *Merge #150*

Author: pedro-ricardo

.vscode/launch.json

@@ -7,22 +7,35 @@
             "type": "extensionHost",
             "request": "launch",
             "runtimeExecutable": "${execPath}",
-            "args": ["--extensionDevelopmentPath=${workspaceRoot}" ],
+            "args": [
+                "--extensionDevelopmentPath=${workspaceFolder}"
+            ],
             "stopOnEntry": false,
             "sourceMaps": true,
-            "outFiles": [ "${workspaceRoot}/out/src/**/*.js" ],
+            "outFiles": [
+                "${workspaceFolder}/out/src/**/*.js"
+            ],
             "preLaunchTask": "npm"
         },
         {
             "name": "Launch Tests",
             "type": "extensionHost",
             "request": "launch",
             "runtimeExecutable": "${execPath}",
-            "args": ["test/resources/sample.f90","--extensionDevelopmentPath=${workspaceRoot}", "--extensionTestsPath=${workspaceRoot}/out/test" ],
+            "env": {
+                "CODE_TESTS_WORKSPACE": "./"
+            },
+            "args": [
+                "test/resources/sample.f90",
+                "--disable-extensions",
+                "--extensionDevelopmentPath=${workspaceFolder}",
+                "--extensionTestsPath=${workspaceFolder}/out/test"
+            ],
             "stopOnEntry": false,
             "sourceMaps": true,
-            "outFiles": [ "${workspaceRoot}/out/test/**/*.js" ],
-            "preLaunchTask": "npm"
+            "outFiles": [
+                "${workspaceFolder}/out/test/**/*.js"
+            ]
         }
     ]
-}
+}

CHANGELOG.md

@@ -7,7 +7,21 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 
 ## [Unreleased]
 
-## [2.1.1] - 2019-xx-xx
+## [2.2.0] - 2020-04-11
+
+### Changed
+
+- Improve syntax highlight (#149, #166, #169)
+- Fix Symbols in VSCode ^1.4x (#154, #140, #151)
+- Dependencies Update (#144, #146, #155)
+- Improve code completion (#148)
+
+### Added
+
+- More custom settings (#152)
+- Breakpoints support (#150)
+
+## [2.1.1] - 2019-06-03
 
 ### Changed
 

README.md

@@ -6,7 +6,7 @@
 [![Installs](https://vsmarketplacebadge.apphb.com/installs/krvajalm.linter-gfortran.svg)](https://marketplace.visualstudio.com/items?itemName=krvajalm.linter-gfortran)
 [![GitHub release](https://img.shields.io/github/release/krvajal/vscode-fortran-support.svg)](https://GitHub.com/krvajal/vscode-fortran-support/releases/)
 
-> This extension provides support for the Fortran programming language. It includes syntax highlighting, code snippets and a linting based on `gfortran`. You can download the Visual Studio Code editor from [here](https://code.visualstudio.com/download).
+> This extension provides support for the Fortran programming language. It includes syntax highlighting, debugging, code snippets and a linting based on `gfortran`. You can download the Visual Studio Code editor from [here](https://code.visualstudio.com/download).
 
 ## Features
 
@@ -16,14 +16,15 @@
 - Code linting based on `gfortran` to show errors wiggles in your code
 - Code autocompletion (beta)
 - Symbols provider
+- Debugger, uses Microsoft's [C/C++ extension](https://github.com/Microsoft/vscode-cpptools)
 
 ![symbol_nav](./doc/symbol_nav.png)
 
 ## Settings
 
 You can control the include paths to be used by the linter with the `fortran.includePaths` setting.
 
-```
+``` jsonc
 {
     "fortran.includePaths": [
         "/usr/local/include",
@@ -34,23 +35,23 @@ You can control the include paths to be used by the linter with the `fortran.inc
 
 By default the `gfortran` executable is assumed to be found in the path. In order to use a different one or if it can't be found in the path you can point the extension to use a custom one with the `fortran.gfortranExecutable` setting.
 
-```
+``` jsonc
 {
-    "fortran.gfortranExecutable": '/usr/local/bin/gfortran-4.7',
+    "fortran.gfortranExecutable": "/usr/local/bin/gfortran-4.7",
 }
 ```
 
 If you want to pass extra options to the `gfortran` executable or override the default one, you can use the setting `fortran.linterExtraArgs`. By default `-Wall` is the only option.
 
-```
+``` jsonc
 {
-    "fortran.linterExtraArgs": ['-Wall'],
+    "fortran.linterExtraArgs": ["-Wall"],
 }
 ```
 
 You can configure what kind of symbols will appear in the symbol list by using
 
-```
+``` jsonc
 {
     "fortran.symbols": [ "function", "subroutine"]
 }
@@ -68,7 +69,7 @@ and by default only functions and subroutines are shown
 
 You can also configure the case for fortran intrinsics auto-complete by using
 
-```
+``` jsonc
 {
     "fortran.preferredCase": "lowercase" | "uppercase"
 }
@@ -90,10 +91,65 @@ This is a list of some of the snippets included, if you like to include addition
 
 To trigger code validations you must save the file first.
 
+## Debugging
+
+The extension uses the debugger from Microsoft's
+[C/C++ extension](https://github.com/Microsoft/vscode-cpptools)
+for Visual Studio Code. This allows this extension to use the full functionality
+of the C/C++ extension for debugging applications:
+(un)conditional breaking points, expression evaluation, multi-threaded debugging,
+call stack, stepping, watch window.
+
+A minimal `launch.json` script, responsible for controlling the debugger, is
+provided below. However, Visual Studio Code is also capable of autogenerating
+a `launch.json` file and the configurations inside the file.
+
+More details about how to setup the debugger can be found in Microsoft's website:
+
+- General information about debugging in VS Code: <https://code.visualstudio.com/docs/editor/debugging>
+- C/C++ extension debugger information: <https://code.visualstudio.com/docs/cpp/cpp-debug>
+- Build tasks for easy compiling: <https://code.visualstudio.com/docs/editor/tasks>
+
+``` jsonc
+{
+    // Use IntelliSense to learn about possible attributes.
+    // Hover to view descriptions of existing attributes.
+    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+    "version": "0.2.0",
+    "configurations": [
+        {
+            "name": "(gdb) Fortran",
+            "type": "cppdbg",
+            "request": "launch",
+            "program": "${workspaceFolder}/a.out",
+            "args": [], // Possible input args for a.out
+            "stopAtEntry": false,
+            "cwd": "${workspaceFolder}",
+            "environment": [],
+            "externalConsole": false,
+            "MIMode": "gdb",
+            "setupCommands": [
+                {
+                    "description": "Enable pretty-printing for gdb",
+                    "text": "-enable-pretty-printing",
+                    "ignoreFailures": true
+                }
+            ]
+        }
+    ]
+}
+```
+
 ## Requirements
 
 For the linter to work you need to have `gfortran` on your path, or wherever you configure it to be.
 
+For debugging you need to have one of the following debuggers installed:
+
+- **Linux**: GDB
+- **macOS**: GDB or LLDB
+- **Windows**: GDB  or Visual Studio Windows Debugger
+
 ## Issues
 
 Please report any issues and feature request on the GitHub repo [here](https://github.com/krvajalmiguelangel/vscode-fortran-support/issues/new)

language-configuration.json

@@ -27,7 +27,7 @@
         },
         {
             "open": "(/",
-            "close": "/)"
+            "close": "/"
         }
     ],
     "surroundingPairs": [