Initial commit for a release

Author: jarrodek

.gitignore

@@ -0,0 +1,5 @@
+.project
+.vscode
+node_modules
+npm-debug.log
+test/playground

.jshintrc

@@ -0,0 +1,21 @@
+{
+  "esnext": true,
+  "node": true,
+  "browser": true,
+  "bitwise": false,
+  "camelcase": false,
+  "curly": true,
+  "eqeqeq": true,
+  "immed": true,
+  "indent": 2,
+  "latedef": true,
+  "noarg": true,
+  "quotmark": "single",
+  "undef": true,
+  "unused": true,
+  "newcap": false,
+  "mocha": true,
+  "globals": {
+
+  }
+}

.travis.yml

@@ -0,0 +1,4 @@
+language: node_js
+node_js: stable
+script:
+- npm test

CHANGELOG.md

@@ -0,0 +1,74 @@
+# Guide for Contributors
+
+The Advanced REST client is open and we encourage the community to contribute in the project. However, it is very important to follow couple of simple rules when you create an issue report or send a pull request.
+
+## Issue reporting
+**If this is feature request**, please provide a clear description of the feature. I've created a [document][87714bdc] that may help you fill up a feature request. But basically you should answer this questions:
+
+- Who will benefit from this feature? _("Someone who is trying to...")_
+- What's the use cases (when the feature will be used)? _("When the HTTP response is...")_
+- What the user gain by having this feature? _("I should be able to see...")_
+
+An overview of the feature would be nice as well.
+
+**When you're filling a bug report**, please be as much specific as you can and:
+
+- A clear description of the bug, logs if available and your expectations. You're welcome to use following template:
+```markdown
+The send button causes the app to close itself.
+
+## Expected outcome
+The app is not closing itself when I try to send a request.
+
+## Actual outcome
+After click it is working for couple of second and the it closes itself.
+
+# Versions
+App: 1.2.3 (check it in app's about page)
+Chrome: Stable (or) 47.0.111.111 (check it in Chrome's about page)
+
+# Steps to reproduce
+1. Turn off CodeMirror
+2. Set method to "PUT"
+3. Use "raw" tab for both payload and headers
+4. Paste following data into the headers field: ...
+5. Paste following data into the payload field: ...
+6. Run the request.
+```
+
+## Submitting Pull Requests
+**While developing**, be sure that you follow the [design guidelines] for ARC.
+
+**Before creating a pull request**, fill up `changelog.md` file inside the elements folder. It is the best way of keeping track of change reasons. Try be very specific and put there only essential information about the changes.
+
+Then a good idea is to test your code. See testing paragraph in the dev-start file. It will save all of us a lot of trouble.
+
+Please ensure that an issue exists for the corresponding change in the pull request that you intend to make. **If an issue does not exist, please create one per the guidelines above**. The goal is to discuss the design and necessity of the proposed change with ARC authors and community before diving into a pull request.
+
+When submitting pull requests, please provide:
+1. **A reference to the corresponding issue** or issues that will be closed by the pull request. Please refer to these issues using the following syntax:
+
+ ```markdown
+ (For a single issue)
+ Fixes #20
+
+ (For multiple issues)
+ Fixes #32, #40
+ ```
+ Github automatically close the issues after merging it to the master. So please, keep the format.
+
+ 2. **A succinct description of the design** used to fix any related issues. For example:
+
+ ```markdown
+ This fixes #20 by removing styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
+ ```
+
+ 3. **At least one test for each bug fixed or feature added** as part of the pull request. Pull requests that fix bugs or add features without accompanying tests will not be considered.
+
+If a proposed change contains multiple commits, please [squash commits](http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash-commits-in-a-github-pull-request) to as few as is necessary to succinctly express the change.
+
+_Part of this document has been copied from Polymer repository. Thanks guys!_
+
+
+  [87714bdc]: https://docs.google.com/document/d/10OPWl9Hagk6Oz--VUztQBTOpm3QP2Vv__PrH3zZ7wFQ/edit?usp=sharing "Feature request file"
+  [Design guidelines]: <https://github.com/jarrodek/ChromeRestClient/wiki/design>

CONTRIBUTING.md

@@ -0,0 +1,79 @@
+Apache License, Version 2.0
+
+
+Apache License
+Version 2.0,
+January 2004
+
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
+2. Grant of Copyright License.
+
+Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License.
+
+Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
+
+4. Redistribution.
+
+You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
+
+You must give any other recipients of the Work or Derivative Works a copy of this License; and You must cause any modified files to carry prominent notices stating that You changed the files; and You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
+
+5. Submission of Contributions.
+
+Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
+
+6. Trademarks.
+
+This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty.
+
+Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability.
+
+In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability.
+
+While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
+
+## Commercial or non open source license
+# Creative Commons Attribution 4.0 International
+
+> Creative Commons Corporation (“Creative Commons”) is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an “as-is” basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible.
+
+## Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses.
+
+Considerations for licensors: Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. More considerations for licensors.
+
+Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor’s permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described. Although not required by our licenses, you are encouraged to respect those requests where reasonable. More considerations for the public.

LICENSE.md

@@ -0,0 +1,78 @@
+# api-console-dependency-manager
+
+https://travis-ci.org/advanced-rest-client/api-console-dependency-manager.svg?branch=master
+
+A npm module to detect and install Mulesoft's API console dependencies.
+
+This module is mainly used in the [api-console-builder](https://github.com/mulesoft-labs/api-console-builder).
+
+## API
+
+Shorthand functions:
+
+-   `installDependencies(workingDir, logger, opts)` -> `new DependendenciesManager#installDependencies(workingDir, logger, opts)`
+
+The module exposes 2 classes:
+
+-   [DependendenciesManager](lib/dependencies.js)
+-   [DependenciesOptions](lib/dependencies-options.js)
+
+### Example
+
+```javascript
+const consoleDependencies = require('api-console-dependency-manager');
+
+consoleDependencies.installDependencies('./build/', console, {
+  verbose: true,
+  parser: true,
+  app: true
+})
+.then(() => console.log('Dependencies are now installed'))
+.catch(cause => console.error(cause));
+```
+
+equivalent to
+
+```javascript
+const {DependendenciesManager, DependenciesOptions} = require('api-console-github-resolver');
+
+const options = new DependenciesOptions({
+  verbose: true,
+  parser: true,
+  app: true
+});
+const workingDir = './build/';
+const logger = console; // Winston or other with console like interface
+const manager = new DependendenciesManager(workingDir, logger, options);
+manager.installDependencies()
+.then(() => console.log('Dependencies are now installed'))
+.catch(cause => console.error(cause));
+```
+
+### DependenciesOptions
+
+| Property | Type | Default | Description |
+| -------- | -------- | -------- | -------- |
+| `verbose` | `Boolean` | `false` | Prints verbose output while installing dependencies. This is used to build install command for bower which is printing console output by default. |
+| `parser` | `Boolean` | `false` | If set it installs RAML javascript parser with the enhancer. |
+| `app` | `Boolean` | `false` | If set it installs `app-route` element to support standalone application architecture of the API console. |
+
+### DependendenciesManager
+
+#### Constructor
+
+##### Arguments
+
+| Property | Type | Description |
+| -------- | -------- | -------- |
+| `workingDir` | `String` | Path to a working directory where the console is processed. Usually it's where the bower.json file is. |
+| `logger` | `Object` | Any logger with the interface compatible with platform's `console` object. |
+| `options` | `Object` or `DependenciesOptions` | Build options passed to the module. |
+
+#### `installDependencies()`
+
+Installs dependencies in the `workingDir`.
+
+##### Return <Promise>
+
+Resolved promise when operation is completed.

README.md

@@ -0,0 +1,34 @@
+'use strict';
+/**
+ * Copyright (C) Mulesoft.
+ * Shared under Apache 2.0 license
+ *
+ * @author Pawel Psztyc <pawel.psztyc@mulesoft.com>
+ */
+/**
+ * Options object for the DependendenciesManager class.
+ */
+class DependenciesOptions {
+  constructor(opts) {
+    opts = opts || {};
+    /**
+     * Prints verbose output while installing dependencies.
+     * This is used to build install command for bower which is printing
+     * console output by default.
+     * @type {Boolean}
+     */
+    this.verbose = typeof opts.verbose === 'boolean' ? opts.verbose : false;
+    /**
+     * If set it installs RAML javascript parser with the enhancer.
+     * @type {Boolean}
+     */
+    this.parser = typeof opts.parser === 'boolean' ? opts.parser : false;
+    /**
+     * If set it installs `app-route` element to support standalone application
+     * architecture of the API console.
+     * @type {Boolean}
+     */
+    this.app = typeof opts.app === 'boolean' ? opts.app : false;
+  }
+}
+exports.DependenciesOptions = DependenciesOptions;