Merge branch 'release-0.4' into master

Author: mikecentola

.eslintignore

@@ -0,0 +1 @@
+vscode.proposed.d.ts

.eslintrc.js

@@ -1,54 +1,22 @@
-/*
-👋 Hi! This file was autogenerated by tslint-to-eslint-config.
-https://github.com/typescript-eslint/tslint-to-eslint-config
-
-It represents the closest reasonable ESLint configuration to this
-project's original TSLint configuration.
-
-We recommend eventually switching this configuration to extend from
-the recommended rulesets in typescript-eslint. 
-https://github.com/typescript-eslint/tslint-to-eslint-config/blob/master/docs/FAQs.md
-
-Happy linting! 💖
-*/
+/**@type {import('eslint').Linter.Config} */
+// eslint-disable-next-line no-undef
 module.exports = {
-    "env": {
-        "es6": true,
-        "node": true
-    },
-    "parser": "@typescript-eslint/parser",
-    "parserOptions": {
-        "sourceType": "module"
-    },
-    "plugins": [
+    root: true,
+    parser: "@typescript-eslint/parser",
+    plugins: [
         "@typescript-eslint"
     ],
-    "rules": {
-        "@typescript-eslint/class-name-casing": "warn",
-        "@typescript-eslint/member-delimiter-style": [
-            "warn",
-            {
-                "multiline": {
-                    "delimiter": "semi",
-                    "requireLast": true
-                },
-                "singleline": {
-                    "delimiter": "semi",
-                    "requireLast": false
-                }
-            }
-        ],
-        "@typescript-eslint/semi": [
-            "warn",
-            "always"
-        ],
-        "curly": "warn",
-        "eqeqeq": [
-            "warn",
-            "always"
-        ],
-        "no-redeclare": "warn",
-        "no-throw-literal": "warn",
-        "no-unused-expressions": "warn"
+    extends: [
+        'eslint:recommended',
+        'plugin:@typescript-eslint/recommended',
+    ],
+    rules: {
+        'semi': [2, "always"],
+        '@typescript-eslint/no-unused-vars': 0,
+        '@typescript-eslint/no-explicit-any': 0,
+        '@typescript-eslint/explicit-module-boundary-types': 0,
+        '@typescript-eslint/no-non-null-assertion': 0,
+        '@typescript-eslint/no-namespace': 0,
+        'no-inner-declarations': 0,
     }
 };

.github/CODEOWNERS

@@ -0,0 +1,3 @@
+# These owners will be the default owners for everything in the repo.
+*       @mikecentola
+

.markdownlint.json

@@ -0,0 +1,6 @@
+{
+    "default": true,
+    "line-length": false,
+    "no-inline-html": false,
+    "first-line-heading": false
+}

.vscode/launch.json

@@ -3,32 +3,34 @@
     "version": "0.2.0",
     "configurations": [
         {
-            "name": "Run Extension",
+            "name": "Launch Extension",
             "type": "extensionHost",
             "request": "launch",
             "runtimeExecutable": "${execPath}",
             "args": [
                 "--disable-extensions",
                 "--extensionDevelopmentPath=${workspaceFolder}"
             ],
+            "stopOnEntry": false,
             "outFiles": [
                 "${workspaceFolder}/out/**/*.js"
             ],
             "preLaunchTask": "${defaultBuildTask}"
         },
         {
-            "name": "Extension Tests",
+            "name": "Launch Extension Tests",
             "type": "extensionHost",
             "request": "launch",
             "runtimeExecutable": "${execPath}",
             "args": [
                 "--extensionDevelopmentPath=${workspaceFolder}",
                 "--extensionsTestsPath=${workspaceFolder}/out/test/suite/index"
             ],
+            "stopOnEntry": false,
             "outFiles": [
                 "${workspaceFolder}/out/**/*.js"
             ],
-            "preLaunchTask": "${defaultBuildTask"
+            "preLaunchTask": "${defaultBuildTask}"
         }
     ]
 }

.vscodeignore

@@ -1,3 +1,4 @@
+.github/**
 .vscode/**
 .vscode-test/**
 out/test/**
@@ -10,4 +11,8 @@ tslint.json
 package-lock.json
 vsc-extension-quickstart.md
 images/*.ai
-images/*.svg
+images/*.svg
+LICENSE
+CONTRIBUTING.md
+node_modules/**
+.eslintignore

CHANGELOG.md

@@ -2,6 +2,38 @@
 
 All changes to vscode-code-syntax will be documented here.
 
+## v0.4.0 [#](https://github.com/appliedengesign/vscode-gcode-syntax/releases/tag/v0.4.0)
+
+Finally a major update to vscode-gcode-syntax!
+
+### New Features
+
+- Added `G65`, `M97` and `M99` to tree info
+- Added spindle speed and direction to tree info
+- Added `M03` and `M04` snippets
+- Added `.001` extension to supported files ( [#11](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/11) )
+- Added Status Bar implementation for Tree messages
+- Added Stats view (Currently only displays number of Tool Changes)
+
+### Fixes
+
+- Added `E` feed rate colorization
+- Fixed mocha test error `useColors -> color`
+- Updated all dependencies
+- Updated copyright info
+- Refactored constants and removed hardcoded manifest
+- Rewrote entire console logging to use Logger class (Future ability to specify log level)
+- Modfied view contexts to change when not viewing g-code instead of hiding views
+- Refactored import declations to improve performance
+- Modified configuration variables
+- Updated README with more information about settings.
+
+### Other
+
+- Added Contributor Covenant
+- Added CODEOWNERS File
+- Added markdownlint config
+
 ## v0.3.3 [#](https://github.com/appliedengesign/vscode-gcode-syntax/releases/tag/v0.3.3)
 
 - Updated dependencies to fix some security vulnerabilities
@@ -10,14 +42,14 @@ All changes to vscode-code-syntax will be documented here.
 
 ## v0.3.2 [#](https://github.com/appliedengesign/vscode-gcode-syntax/releases/tag/v0.3.2)
 
-- Fixed Markup with division symbol [#9](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/7)
+- Fixed Markup with division symbol ( [#9](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/7) )
 - Fixed typo in src manifest
 - Updated dependencies
 
 ## v0.3.1 [#](https://github.com/appliedengesign/vscode-gcode-syntax/releases/tag/v0.3.1)
 
 - Added ```.prg``` file extension [#7](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/7)
-- Moved activity bar icon into resources folder. [#5](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/5)
+- Moved activity bar icon into resources folder. ( [#5](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/5) )
 
 ## v0.3.0 [#](https://github.com/appliedengdesign/vscode-gcode-syntax/releases/tag/v0.3.0)
 
@@ -28,8 +60,8 @@ All changes to vscode-code-syntax will be documented here.
 ## v0.2.0 [#](https://github.com/appliedengdesign/vscode-gcode-syntax/releases/tag/v0.2.0)
 
 - Refactor extension code for new vscode extension syntax
-- Added ```.eia``` file extension [#4](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/4)
-- Fixed compound macro variable syntax highlighting [#3](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/4)
+- Added ```.eia``` file extension ( [#4](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/4) )
+- Fixed compound macro variable syntax highlighting ( [#3](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/3) )
 - Updated dependencies & dev dependencies
 - Added standard vscode testing to source code
 - Added dedicated output channel "G-Code" when activated
@@ -41,8 +73,8 @@ All changes to vscode-code-syntax will be documented here.
 
 ## v0.1.1 [#](https://github.com/appliedengdesign/vscode-gcode-syntax/releases/tag/v0.1.1)
 
-- Fixed Incorrect highlighting for DO / END - [#2](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/2)
-- Fixed Math expressions incorrectly highlighted -  [#1](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/1)
+- Fixed Incorrect highlighting for DO / END ( [#2](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/2) )
+- Fixed Math expressions incorrectly highlighted ( [#1](https://github.com/appliedengdesign/vscode-gcode-syntax/issues/1) )
 
 ## v0.1.0 [#](https://github.com/appliedengdesign/vscode-gcode-syntax/releases/tag/v0.1.0)
 

CODE_OF_CONDUCT.md

@@ -0,0 +1,129 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2019 Applied Engineering & Design
+Copyright (c) 2020 Applied Engineering & Design
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal