Merge pull request #23 from halcyon-tech/feature/tests

Unit tests & local file support

.eslintignore

@@ -0,0 +1 @@
+dist

README.md

@@ -11,6 +11,12 @@ Adds functionality to improve writing RPGLE free-format (only `**FREE`), includi
 
 Depends on Code for IBM i due to source code living on the remote system.
 
+## FAQ
+
+1. **Does this only work with free-format?** The content assist and outline view only works with completely free-format (`**FREE`). The column assist is for fixed-format.
+2. **My copybook is not opening or prototypes are not coming from my copybook.** Right now, it is an explicit path to your member or streamfile. For example, if you're editing `YOURLIB/QRPGLESRC/HELLOWORLD.rpgle` and your copybook path is `QRPGLEREF,PRTYPE`, then it will assume the library of `YOURLIB`. For streamfiles, it will be relative to your working directory. For local files, it will be your VS Code workspace.
+3. **Does this work with local projects?** Yes! But, your local RPGLE must be the IFS style path on your `copy` and `include` directives.
+
 ## How to enable
 
 Enable these options in VS Code settings.
@@ -22,6 +28,14 @@ Enable these options in VS Code settings.
 * `vscode-rpgle.rpgleLinterSupportEnabled` - enables linter
    * `vscode-rpgle.openLintConfig` to open or create linter file. Creates / opens relative to source that is currently open. Read more below on linting.
 
+## Developing
+
+1. Fork & clone
+2. `npm i`
+3. Run
+   * `npm run test`
+   * Debug 'Run Extension'
+
 # Linter
 
 The linter configuration is held in a JSON document relative to the RPGLE source code that is being worked on.