Merge pull request #105 from imgix/beta

Author: frederickfogerty

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,45 @@
+---
+name: Bug report
+about: Create a report to help us improve
+---
+
+**Before you submit:**
+
+- [ ] Please search through the existing issues (both open AND closed) to see if your issue has been discussed before. Github issue search can be used for this: https://github.com/imgix/vue-imgix/issues?utf8=%E2%9C%93&q=is%3Aissue
+- [ ] Please ensure the problem has been isolated and reduced. This link explains more: http://css-tricks.com/6263-reduced-test-cases/
+
+**Describe the bug**
+A clear and concise description of what the bug is. Please strive to reach the **root problem** of your issue to avoid the XY problem. See more: https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem
+
+**To Reproduce**
+A bug is a _demonstrable problem_ that is caused by the code in the repository. Thus, the contributors need a way to reproduce your issue - if we can't reproduce your issue, we can't help you! Also, please be as detailed as possible.
+
+[a link to a codesandox or repl.it; here is a link to a codesandbox with vue-imgix installed which can be forked: https://codesandbox.io/s/vue-imgix-base-codesandbox-bhz8n]
+
+[alternatively, please provide a code example]
+
+```js
+// A *self-contained* demonstration of the problem follows...
+// This should be able to be dropped into a file with vue-imgix installed and just work
+```
+
+Steps to reproduce the behaviour:
+
+1.  Go to '...'
+2.  Click on '....'
+3.  Scroll down to '....'
+4.  See error
+
+**Expected behaviour**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Information:**
+
+- vue-imgix version: [e.g. v1.0]
+- browser version: [include link from [https://www.whatsmybrowser.org/](https://www.whatsmybrowser.org/) or details about the OS used and browser version]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,21 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+---
+
+**Before you submit:**
+
+- [ ] Please search through the existing issues (both open AND closed) to see if your feature has already been discussed. Github issue search can be used for this: https://github.com/imgix/vue-imgix/issues?utf8=%E2%9C%93&q=is%3Aissue
+- [ ] Please take a moment to find out whether your idea fits with the scope and aims of the project
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of how this feature would function.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,11 @@
+---
+name: Question
+about: Ask a question about the project
+---
+
+**Before you submit:**
+
+- [ ] Please search through the existing issues (both open AND closed) to see if your question has already been discussed. Github issue search can be used for this: https://github.com/imgix/vue-imgix/issues?utf8=%E2%9C%93&q=is%3Aissue
+
+**Question**
+A clear and concise description of your question

.github/pull_request_template.md

@@ -0,0 +1,77 @@
+<!-- prettier-ignore-start -->
+<!--
+Hello, and thanks for contributing to vue-imgix! 🎉🙌
+Please take a second to fill out PRs with the following template!
+-->
+
+## Description
+<!-- What is accomplished by this PR? If there is something potentially controversial in your PR, please take a moment to tell us about your choices. -->
+
+
+
+<!-- 
+Please use the checklist that is most closely related to your PR, and delete the other checklists. -->
+## Checklist: Fixing typos/Doc change
+
+- [ ] The target branch is `beta`. This is important for our CI/CD config.
+- [ ] Each commit follows the conventional commit spec format: e.g. `chore(readme): fixed typo`. See the end of this file for more information.
+
+## Checklist: Bug Fix
+
+- [ ] The target branch is `beta`. This is important for our CI/CD config.
+- [ ] Each commit follows the conventional commit spec format: e.g. `chore(readme): fixed typo`. See the end of this file for more information.
+- [ ] All existing unit tests are still passing (if applicable)
+- [ ] Add new passing unit tests to cover the code introduced by your PR
+- [ ] Update the readme
+- [ ] Update or add any necessary API documentation
+- [ ] Add some [steps](#steps-to-test) so we can test your bug fix
+
+## Checklist: New Feature
+
+- [ ] The target branch is `beta`. This is important for our CI/CD config.
+- [ ] Each commit follows the conventional commit spec format: e.g. `chore(readme): fixed typo`. See the end of this file for more information.
+- [ ] Any breaking changes are specified on the commit on which they are introduced with `BREAKING CHANGE` in the body of the commit.
+- [ ] If this is a big feature with breaking changes, consider [opening an issue][issues] to discuss first. This is completely up to you, but please keep in mind that your PR might not be accepted.
+- [ ] Run unit tests to ensure all existing tests are still passing
+- [ ] Add new passing unit tests to cover the code introduced by your PR
+- [ ] Update the readme
+- [ ] Add some [steps](#steps-to-test) so we can test your cool new feature!
+
+## Steps to Test
+
+<!-- Delete this selction if you are just submitting a doc change/small fix -->
+
+<!-- A code example or a set of steps is preferred -->
+
+Related issue: [e.g. #42]
+
+Code:
+
+```js
+// A standalone JS example of what the PR solves
+```
+
+<!-- A link to a codepen/codesandbox is also an option. -->
+
+Steps:
+
+1.  Go to '...'
+2.  Click on '....'
+3.  Scroll down to '....'
+4.  See that the error has been fixed
+
+
+
+
+
+<!--
+
+## Conventional Commit Spec
+
+PR titles should be in the format `<type>(<scope>): <description>`. For example: `chore(readme): fix typo`
+
+`type` can be one of `feat`, `fix`, `test`, or `chore`.
+`scope` is optional, and can be anything.
+`description` should be a short description of the change, in past tense.
+-->
+<!-- prettier-ignore-end -->

.travis.yml

@@ -18,6 +18,7 @@ cache:
 install:
   - yarn install --frozen-lockfile
 script:
+  - yarn build
   - yarn lint:ci
   - yarn test:unit
   - yarn test:e2e --headless
@@ -26,11 +27,13 @@ branches:
   only:
     - master
     - next
+    - beta
+    - alpha
 
 deploy:
   provider: script
   skip_cleanup: true
   script:
     - npx semantic-release
   on:
-    branch: next
+    all_branches: true

.vscode/settings.json

@@ -1,7 +1,7 @@
 {
-  "editor.formatOnSave": true,
+  "editor.formatOnSave": false,
   "vetur.validation.template": false,
   "editor.codeActionsOnSave": {
     "source.fixAll.eslint": true
-  }
+  },
 }

LICENSE

@@ -1,21 +1,24 @@
-MIT License
+Copyright (c) 2020 Zebrafish Labs  
+All rights reserved.
 
-Copyright (c) 2020 imgix
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
 
-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:
+1. Redistributions of source code must retain the above copyright notice,
+   this list of conditions and the following disclaimer.
 
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
 
-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.
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.