add elm syntax highlighting (codesandbox#2036)

* add elm syntax highlighting

* only add syntax highlight

Author: SaraVieira

standalone-packages/vscode-extensions/out/extensions/index.json

@@ -0,0 +1,22 @@
+sudo: false
+
+os:
+  - osx
+  - linux
+    
+before_install:
+  - if [ $TRAVIS_OS_NAME == "linux" ]; then
+      export CXX="g++-4.9" CC="gcc-4.9" DISPLAY=:99.0;
+      sh -e /etc/init.d/xvfb start;
+      sleep 3;
+    fi
+    
+install:
+  - node --version
+  - npm --version
+  - npm install -g elm
+  - npm install
+  - npm run vscode:prepublish
+    
+script:
+  - npm test

standalone-packages/vscode-extensions/out/extensions/sbrink.elm-0.25.0/.travis.yml

@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="utf-8"?>
+<PackageManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011" xmlns:d="http://schemas.microsoft.com/developer/vsx-schema-design/2011">
+  <Metadata>
+    <Identity Language="en-US" Id="elm" Version="0.25.0" Publisher="sbrink"/>
+    <DisplayName>elm</DisplayName>
+    <Description xml:space="preserve">Elm Language Support for Visual Studio Code</Description>
+    <Tags>snippet,keybindings,json,elm,Elm,__ext_elm</Tags>
+    <Categories>Programming Languages,Snippets,Linters</Categories>
+    <GalleryFlags>Public</GalleryFlags>
+    <Badges></Badges>
+    <Properties>
+      <Property Id="Microsoft.VisualStudio.Code.Engine" Value="^1.6.0" />
+      <Property Id="Microsoft.VisualStudio.Code.ExtensionDependencies" Value="" />
+      <Property Id="Microsoft.VisualStudio.Code.ExtensionPack" Value="" />
+      <Property Id="Microsoft.VisualStudio.Code.LocalizedLanguages" Value="" />
+      
+        <Property Id="Microsoft.VisualStudio.Services.Links.Source" Value="https://github.com/Krzysztof-Cieslak/vscode-elm.git" />
+        <Property Id="Microsoft.VisualStudio.Services.Links.Getstarted" Value="https://github.com/Krzysztof-Cieslak/vscode-elm.git" />
+        
+          <Property Id="Microsoft.VisualStudio.Services.Links.GitHub" Value="https://github.com/Krzysztof-Cieslak/vscode-elm.git" />
+        
+      
+      <Property Id="Microsoft.VisualStudio.Services.Links.Support" Value="https://github.com/Krzysztof-Cieslak/vscode-elm/issues" />
+      
+      <Property Id="Microsoft.VisualStudio.Services.Branding.Color" Value="#232323" />
+      <Property Id="Microsoft.VisualStudio.Services.Branding.Theme" Value="dark" />
+      <Property Id="Microsoft.VisualStudio.Services.GitHubFlavoredMarkdown" Value="true" />
+      
+      
+    </Properties>
+    
+    <Icon>extension/images/elmIcon.png</Icon>
+  </Metadata>
+  <Installation>
+    <InstallationTarget Id="Microsoft.VisualStudio.Code"/>
+  </Installation>
+  <Dependencies/>
+  <Assets>
+    <Asset Type="Microsoft.VisualStudio.Code.Manifest" Path="extension/package.json" Addressable="true" />
+    <Asset Type="Microsoft.VisualStudio.Services.Content.Details" Path="extension/README.md" Addressable="true" /><Asset Type="Microsoft.VisualStudio.Services.Content.Changelog" Path="extension/CHANGELOG.md" Addressable="true" /><Asset Type="Microsoft.VisualStudio.Services.Icons.Default" Path="extension/images/elmIcon.png" Addressable="true" />
+  </Assets>
+</PackageManifest>

standalone-packages/vscode-extensions/out/extensions/sbrink.elm-0.25.0/.vsixmanifest

@@ -0,0 +1,132 @@
+### 0.25.0 - 07.01.2019
+* Fix issue with elm module parser using object spread in raw javascript (not transpiled). (by @joeandaverde)
+* Fix issue with improperly invaliding old symbols in cache. (by @joeandaverde)
+* Fix elm analyse path (by @Razzeee)
+* The linter should also respect the module in "Make special path" (by @ccapndave)
+
+### 0.24.0 - 26.11.2018
+* Improved Symbol Search / Goto Definition (by @joeandaverde)
+* Fix wrong missing compiler error message (by @andys8)
+* Check isTestFile before normalizing path on windows (by @Krzysztof-Cieslak)
+
+### 0.23.0 - 19.11.2018
+* corrected a spelling error (by @WEBhicham)
+* Replace inefficient regex to locate imports with simpler regex (by @joeandaverde)
+* Add json schema support for Elm's config files (by @stephenreddek)
+* Add support for running tests for Elm 0.19 (by @jackfranklin)
+
+### 0.22.0 - 01.10.2018
+* Fix a 0.18 elm-make configuration bug and support elm-format for 0.18 and 0.19 (by @hakonrossebo)
+* Setting and logic to disable linting (by @hakonrossebo)
+* Adds external package "oracle"-support for Elm 0.19 (by @r1sc)
+* Handle breaking change in elm-format (by @hakonrossebo)
+
+### 0.21.0 - 30.08.2018
+* Set elm-make as default makeCommand for 0.18 and earlier (by @jackfranklin)
+* Fix for Elm 0.19, find right project directory (by @norpan)
+* Fix linting for errors for Elm 0.18 (by @jackfranklin)
+* Changes REPL to use integrated terminal for interactivity (by @hakonrossebo)
+* Make compiler errors a little easier to read (by @norpan)
+* Separate example code for 0.18 and 0.19 (by @hakonrossebo)
+* Fixes to omit Elm Oracle for 0.19 and read elm.json (by @hakonrossebo)
+* Using terminal instead of output window to install packages for y/n (by @hakonrossebo)
+
+### 0.20.0 - 24.08.2018
+* Snippets: Let expression indentation (elm-format) (by @andys8)
+* Add ability to configure elm-package locating. (by @jackfranklin)
+* Syntax Polish (by @mdgriffith)
+* Elm 0.19 update (by @hakonrossebo and @7sharp9)
+
+### 0.19.0 - 27.07.2018
+* Snippets: Add todo comment snippet (by @andys8)
+* Refactoring diagnostic init for LS (by @lostintangent)
+* Grammar updates (by @mdgriffith)
+* Compilable Msg placeholder in HTML.program snippet (by @milesfrain)
+* Info about editor.formatOnSaveTimeout on Windows (by @rofrol)
+
+### 0.18.0 - 22.05.2018
+* Make linting work again with elm-analyse 0.14.2 (by @Yarith)
+* Handle formatSelection the same as formatDocument (by @milesfrain)
+
+### 0.17.0 - 26.04.2018
+* Limiting workspace symbols and linting to local files (by @lostintangent)
+* Fixed issue with elm-make and spaces in paths (by @Arbyy)
+* Fix error message not clearing when formatting with elm-format (by @adam77)
+* Make folding not eat up empty lines (by @szabba)
+
+### 0.16.0 - 11.02.2018
+*  Jump to symbol based on imports. Jump to symbol that has been fully qualified such as `MyModule.myFunction` (by @joeandaverde)
+* Fix cursor moving when formatting with elm-format (by @adam77)
+* Support elm code syntax highlighting in markdown files (by @kachkaev)
+* Snippets improvement (by @andys8)
+* Fix `elm.makeCommand` sample path for Windows (by @lukaszgasior)
+
+### 0.15.1 - 03.10.2017
+* added prettier to the project (by @littleStudent)
+* Fix package installation  (by @wolverian)
+* save file only once formatting is finished (by @gyzerok)
+* Snippets for elm-test test and describe blocks (by @andys8 )
+
+### 0.15.0 - 10.08.2017
+* Add integration with `Elm-analyse` (by @hakonrossebo)
+* Use TsLint on `vscode-elm` code base (by @littleStudent)
+
+### 0.14.1 - 21.06.2017
+* Added the ability to include function/type/type alias comments in intellisense (by @andrewsdev)
+* Fixed bugs in parsing elm-oracle hover results and bugs in userProject hover results (by @andrewsdev)
+
+### 0.14.0 - 15.06.2017
+* Fix defaultModel snippet, Add Html.program snippet (by @iocube)
+* Bugfix: Error with one-line suggested annotation (by @hakonrossebo)
+* Handle block comments (by @hakonrossebo)
+* Improvements/bug fixes for user project intellisense (by @andrewsdev):
+  - Bug fix: writing type signature before writing the function definition behavior
+  - Bug fix: `/as/` regex for the list of imports behavior
+  - Bug fix: name of a user's type or type alias were not included in intellisense results
+  - Feature: Primitive types are now included in autocomplete when writing a function definition
+  - Feature: limit on user intellisense 'comment' size now better indicates it has hit a settings limit
+  - Feature: Can now set `elm.userProjectMaxCommentSize` to 0 to bypass the limit on user intellisense 'comment' size
+  - Feature: Working Intellisense (hover and autocomplete) for user modules with a '.'. Custom configuration to control this feature.
+
+### 0.13.0 - 08.06.2017
+* Workspace symbols implementation (by @hakonrossebo)
+* Elm-reactor subdir traversal (by @hakonrossebo)
+* Command to stop Elm REPL (by @hakonrossebo)
+* Elm-make uses path correctly. Also introduce special file config (by @hakonrossebo)
+
+### 0.12.0 - 03.06.2017
+* add auto-closing quotes to config (by @kojuro-kun)
+* Changes snippets to 4 space indentation (by @hakonrossebo)
+* Fixes double module name in autocomplete (by @hakonrossebo)
+* Autocomplete handles aliased module names (by @hakonrossebo)
+* Elm-format error as StatusBar instead of ErrorMessage (by @hakonrossebo)
+* Initial implementation of CodeActions (function type annotations, misspelled variable names, types and patterns) (by @hakonrossebo)
+* Implements go to definition for document (by @hakonrossebo)
+
+### 0.11.2 - 10.05.2017
+* Improved Linter so that issues are associated with the correct files (by @danheuck )
+* Fix for elm-oracle being fed entire elm file (by @dannyob)
+
+### 0.11.1 - 10.05.2017
+* Fix keyboard shortcuts
+
+### 0.11.0 - 08.05.2017
+* Add `Elm: Browse package` command
+* Fix paths concatenation issue for non-Windows machines
+
+### 0.10.0 - 05.05.2017
+
+* Initial changelog entry, so all working features are listed:
+
+* Syntax highlighting
+* Autocomplete (for external packages and experimentally for local projects)
+* Error highlighting
+* Code formatting
+* Hover info (for external packages and experimentally for local projects)
+* Document Symbol provider
+* Integration with Elm Reactor
+* Integration with Elm Make
+* Integration with Elm Package
+* REPL support
+* Custom Elm Snippets
+

standalone-packages/vscode-extensions/out/extensions/sbrink.elm-0.25.0/CHANGELOG.md

@@ -0,0 +1,172 @@
+# Contributing to VScode-Elm
+
+Please take a moment to review this document in order to make the contribution
+process easy and effective for everyone involved!
+
+## Using the issue tracker
+
+Use the issues tracker for:
+
+* [bug reports](#bug-reports)
+* [feature requests](#feature-requests)
+* [submitting pull requests](#pull-requests)
+
+Please **do not** use the issue tracker for personal or commercial support requests.
+
+Personal support request should be discussed on Elm Slack.
+
+Comercial support is provided by [Lambda Factory](http://lambdafactory.io/).
+
+## Bug reports
+
+A bug is either a _demonstrable problem_ that is caused by the code in the repository,
+or indicate missing, unclear, or misleading documentation. Good bug reports are extremely
+helpful - thank you!
+
+Guidelines for bug reports:
+
+1. **Use the GitHub issue search** — check if the issue has already been
+   reported.
+
+2. **Check if the issue has been fixed** — try to reproduce it using the
+   `master` branch in the repository.
+
+3. **Isolate and report the problem** — ideally create a reduced test
+   case.
+
+Please try to be as detailed as possible in your report. Include information about
+your Operating System, as well as your `elm` version. Please provide steps to
+reproduce the issue as well as the outcome you were expecting! All these details
+will help developers to fix any potential bugs.
+
+Example:
+
+> Short and descriptive example bug report title
+>
+> A summary of the issue and the environment in which it occurs. If suitable,
+> include the steps required to reproduce the bug.
+>
+> 1. This is the first step
+> 2. This is the second step
+> 3. Further steps, etc.
+>
+> `<url>` - a link to the reduced test case (e.g. a GitHub Gist)
+>
+> Any other information you want to share that is relevant to the issue being
+> reported. This might include the lines of code that you have identified as
+> causing the bug, and potential solutions (and your opinions on their
+> merits).
+
+## Feature requests
+
+Feature requests are welcome and should be discussed on issue tracker. But take a moment to find
+out whether your idea fits with the scope and aims of the project. It's up to *you*
+to make a strong case to convince the community of the merits of this feature.
+Please provide as much detail and context as possible.
+
+
+## Pull requests
+
+Good pull requests - patches, improvements, new features - are a fantastic
+help. They should remain focused in scope and avoid containing unrelated
+commits.
+
+**IMPORTANT**: By submitting a patch, you agree that your work will be
+licensed under the license used by the project.
+
+If you have any large pull request in mind (e.g. implementing features,
+refactoring code, etc), **please ask first** otherwise you risk spending
+a lot of time working on something that the project's developers might
+not want to merge into the project.
+
+Please adhere to the coding conventions in the project (indentation,
+accurate comments, etc.) and don't forget to add your own tests and
+documentation. When working with git, we recommend the following process
+in order to craft an excellent pull request:
+
+1. [Fork](https://help.github.com/articles/fork-a-repo/) the project, clone your fork,
+   and configure the remotes:
+
+   ```bash
+   # Clone your fork of the repo into the current directory
+   git clone https://github.com/<your-username>/vscode-elm
+   # Navigate to the newly cloned directory
+   cd vscode-elm
+   # Assign the original repo to a remote called "upstream"
+   git remote add upstream https://github.com/Krzysztof-Cieslak/vscode-elm
+   ```
+
+2. If you cloned a while ago, get the latest changes from upstream, and update your fork:
+
+   ```bash
+   git checkout master
+   git pull upstream master
+   git push
+   ```
+
+3. Create a new topic branch (off of `master`) to contain your feature, change,
+   or fix.
+
+   **IMPORTANT**: Making changes in `master` is discouraged. You should always
+   keep your local `master` in sync with upstream `master` and make your
+   changes in topic branches.
+
+   ```bash
+   git checkout -b <topic-branch-name>
+   ```
+4. Install dependencies and make sure everything is building
+
+  ```bash
+  yarn install
+  yarn build
+  ```
+
+5. Open extension in your favorite editor (we recomend VSCode as it enables easy desbuging of the plugin)
+
+  ```bash
+  code .
+  ```
+
+6. Start watch-mode compilation (re-compilation on every file save)
+
+  ```bash
+  yarn run compile
+  ```
+
+7. You can start current version of the extension in experimental
+   instance of VSCode with `Launch Extension` debug configuration (`F5`).
+
+8. Commit your changes in logical chunks. Keep your commit messages organized,
+   with a short description in the first line and more detailed information on
+   the following lines. Feel free to use Git's
+   [interactive rebase](https://help.github.com/articles/about-git-rebase/)
+   feature to tidy up your commits before making them public.
+
+9. Make sure all the tests are still passing.
+
+   ```bash
+   yarn test
+   ```
+
+10. Push your topic branch up to your fork:
+
+   ```bash
+   git push origin <topic-branch-name>
+   ```
+
+11. [Open a Pull Request](https://help.github.com/articles/about-pull-requests/)
+    with a clear title and description.
+
+12. If you haven't updated your pull request for a while, you should consider
+   rebasing on master and resolving any conflicts.
+
+   **IMPORTANT**: _Never ever_ merge upstream `master` into your branches. You
+   should always `git rebase` on `master` to bring your changes up to date when
+   necessary.
+
+   ```bash
+   git checkout master
+   git pull upstream master
+   git checkout <your-topic-branch>
+   git rebase master
+   ```

standalone-packages/vscode-extensions/out/extensions/sbrink.elm-0.25.0/CONTRIBUTING.md

@@ -0,0 +1,17 @@
+Copyright (c) Sascha Brink, Krzysztof Cieslak
+
+All rights reserved.
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy,
+modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software
+is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
+BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
+OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.