Merge tag '3.5.3' of https://github.com/woocommerce/woocommerce

.babelrc

@@ -0,0 +1,9 @@
+{
+	"presets": [
+		"es2015",
+		"stage-2"
+	],
+	"plugins": [
+		"add-module-exports"
+	]
+}

.codeclimate.yml

@@ -0,0 +1,37 @@
+engines:
+  phpcodesniffer:
+    enabled: true
+    config:
+      standard: "WordPress"
+  eslint:
+    enabled: true
+  scss-lint:
+    enabled: true
+  duplication:
+    enabled: true
+    config:
+      languages:
+      - php
+      - javascript
+ratings:
+  paths:
+   - "includes/*"
+exclude_paths:
+- "tests/"
+- "apigen/"
+- "sample-data/"
+- "i18n/"
+- "includes/api/legacy/"
+- "includes/libraries/"
+- "includes/updates/"
+- "includes/gateways/simplify-commerce/"
+- "includes/shipping/legacy-*"
+- "includes/wc-deprecated-functions.php"
+- "assets/js/accounting/"
+- "assets/js/jquery-*"
+- "assets/js/prettyPhoto/"
+- "assets/js/round/"
+- "assets/js/select2/"
+- "assets/js/selectWoo/"
+- "assets/js/stupidtable/"
+- "assets/js/zeroclipboard/"

.codecov.yml

@@ -0,0 +1,26 @@
+codecov:
+  notify:
+    require_ci_to_pass: yes
+
+coverage:
+  precision: 2
+  round: nearest
+  range: "50...100"
+
+  status:
+    project: yes
+    patch: off
+    changes: off
+
+parsers:
+  gcov:
+    branch_detection:
+      conditional: yes
+      loop: yes
+      method: no
+      macro: no
+
+comment:
+  layout: "files"
+  behavior: default
+  require_changes: yes

.editorconfig

@@ -0,0 +1,24 @@
+# This file is for unifying the coding style for different editors and IDEs
+# editorconfig.org
+
+# WordPress Coding Standards
+# https://make.wordpress.org/core/handbook/coding-standards/
+
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+indent_size = 4
+tab_width = 4
+indent_style = tab
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.txt]
+trim_trailing_whitespace = false
+
+[*.{md,json,yml}]
+trim_trailing_whitespace = false
+indent_style = space
+indent_size = 2

.gitattributes

@@ -0,0 +1,12 @@
+/.* export-ignore
+apigen* export-ignore
+CODE_OF_CONDUCT.md export-ignore
+CHANGELOG.txt export-ignore
+composer.* export-ignore
+Gruntfile.js export-ignore
+package.json export-ignore
+package-lock.json export-ignore
+phpcs.xml export-ignore
+phpunit.* export-ignore
+README.md export-ignore
+tests export-ignore

.github/CONTRIBUTING.md

@@ -0,0 +1,94 @@
+# Contributing to WooCommerce ✨
+
+There are many ways to contribute to the WooCommerce project!
+
+- Translating strings into your language.
+- Answering questions on GitHub and within the various WooCommerce communities.
+- Submitting fixes, improvements, and enhancements.
+
+WooCommerce currently powers 30% of all online stores across the internet, and your help making it even more awesome will be greatly appreciated :)
+
+If you think something can be improved and you wish to contribute code,
+[fork](https://help.github.com/articles/fork-a-repo/) WooCommerce, commit your changes,
+and [send a pull request](https://help.github.com/articles/using-pull-requests/). We'll be happy to review your changes!
+
+## Feature Requests
+
+Feature requests can be [submitted to our issue tracker](https://github.com/woocommerce/woocommerce/issues/new?template=Feature_request.md). Be sure to include a description of the expected behavior and use case, and before submitting a request, please search for similar ones in the closed issues.
+
+Feature request issues will remain closed until we see sufficient interest via comments and [👍 reactions](https://help.github.com/articles/about-discussions-in-issues-and-pull-requests/) from the community.
+
+You can see a [list of current feature requests which require votes here](https://github.com/woocommerce/woocommerce/issues?q=label%3A%22votes+needed%22+label%3Aenhancement+sort%3Areactions-%2B1-desc+is%3Aclosed).
+
+## Technical Support / Questions
+
+We don't offer technical support on GitHub so we recommend using the following:
+
+**Reading our documentation**
+Usage docs can be found here: https://docs.woocommerce.com/
+
+If you have a problem, you may want to start with the self help guide here: https://docs.woocommerce.com/document/woocommerce-self-service-guide/
+
+**Technical support for premium extensions or if you're a WooCommerce.com customer**
+ from a human being - submit a ticket via the helpdesk
+https://woocommerce.com/contact-us/ 
+
+**General usage and development questions**
+- WooCommerce Slack Community: https://woocommerce.com/community-slack/
+- WordPress.org Forums: https://wordpress.org/support/plugin/woocommerce
+- The WooCommerce Help and Share Facebook group
+
+**Customizations**
+- [WooExperts](https://woocommerce.com/experts/)
+- [Codeable](https://codeable.io/)
+
+## Coding Guidelines
+
+- **Ensure you stick to the [WordPress Coding Standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/)**
+- Install our pre-commit hook using composer. It'll help with the Coding Standards. To install run `composer install` from the command line within the woocommerce plugin directory.
+- Ensure you use LF line endings in your code editor. Use [EditorConfig](http://editorconfig.org/) if your editor supports it so that indentation, line endings and other settings are auto configured.
+- When committing, reference your issue number (#1234) and include a note about the fix.
+- Ensure that your code is compatible with PHP 5.2+.
+- Push the changes to your fork and submit a pull request on the master branch of the WooCommerce repository. Existing maintenance branches will be maintained by WooCommerce developers.
+
+Please **don't** modify the changelog or update the .pot files. These will be maintained by the WooCommerce team.
+
+## Translating WooCommerce
+
+We have a [project on translate.wordpress.org](https://translate.wordpress.org/projects/wp-plugins/woocommerce). You can join the localization team of your language and help by translating WooCommerce. [Find more about using joining a language team and using GlotPress](https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/).
+
+If WooCommerce is already 100% translated for your language, join the team anyway! We regularly update our language files and there will definitely be need of your help soon.
+
+### Glossary & Style Guide
+
+Please refer to this page on the [Translator Handbook](https://make.wordpress.org/polyglots/handbook/translating/glossary-style-guide/) for information about the glossary and the style guide.
+
+We maintain the WooCommerce glossary [on this shared Google Sheet](https://docs.google.com/spreadsheets/d/1Pobl2nNWieaSpZND9-Bwa4G8pnMU7QYceKsXuWCwSxQ/edit?usp=sharing). You can use it as a template for creating your own glossary.
+Please download the file by going to **File > Download as > Comma-separated values (.csv, current sheet)** and save it on your computer/Mac. Open it with your favourite CSV editor (or re-upload it on your own Google Drive) and edit it.
+
+Make sure to edit the second column’s header by using your own language’s code (eg. for Italian you would use `it`, for Portuguese (Brazil) you would use `pt-BR`).
+
+Write the translated entry in this column and translate the entry description as well.
+Don’t change other columns headers and value, but feel free to add new entries.
+
+When your CSV is ready, import it on GlotPress.
+
+_**Warning**: Importing a CSV does not replace existing items, they will be created again. We suggest to import them only when first creating the glossary._
+
+Each translation editor will take care of updating the glossary on GlotPress by editing/adding items when needed.
+
+_**Note**: Only editors can create/import and edit glossaries and glossary items on GlotPress. Anyone can suggest new items to add to the glossary or translate them._
+
+**Style Guides Available**
+
+We don’t have a Style Guide template available, so feel free to create your own. Here are the style guides available at the moment:
+
+* [Italian](https://docs.google.com/document/d/1rspopHOiTL-5-PjyG5eJxjkYk6JkzqVbyS24OdA052o/edit?usp=sharing)
+
+If you created a style guide for your language, please let us know so we can add it in the list above. You can also add it by yourself by submitting a PR for this file.
+
+### Translating Video Tutorials
+
+Another valuable way to help is by translating our growing library of WooCommerce video tutorials. Check out the [Translating  Our Videos](https://docs.woocommerce.com/document/translating-our-videos/) doc and join in!
+
+By translating video tutorials you'll be helping non-English speaking users and people affected by disabilities to get to grips with using WooCommerce for the first time, and to go on and create their businesses and make a living! That's something to be proud of and if you choose to dive into this area, we salute you.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,48 @@
+<!-- This form is for reporting bugs and issues specific to the WooCommerce plugin. This is not a support portal. If you need technical support from a human being, please submit a ticket via the helpdesk instead: https://woocommerce.com/contact-us/ -->
+
+<!-- Usage questions can also be directed to the public support forum here: https://wordpress.org/support/plugin/woocommerce, unless this is a question about a premium extension in which case you should use the helpdesk. -->
+
+<!-- If you have a feature request, submit it to: http://ideas.woocommerce.com/forums/133476-woocommerce -->
+
+<!-- If you are a developer who needs a new filter/hook raise a PR instead :) -->
+
+<!-- Please be as descriptive as possible; issues lacking the below details, or for any other reason than to report a bug, may be closed without action. -->
+
+## Prerequisites
+
+<!-- MARK COMPLETED ITEMS WITH AN [x] -->
+
+- [ ] I have searched for similar issues in both open and closed tickets and cannot find a duplicate
+- [ ] The issue still exists against the latest `master` branch of WooCommerce on Github (this is **not** the same version as on WordPress.org!)
+- [ ] I have attempted to find the simplest possible steps to reproduce the issue
+- [ ] I have included a failing test as a pull request (Optional)
+
+## Steps to reproduce the issue
+
+<!-- We need to be able to reproduce the bug in order to fix it so please be descriptive! -->
+
+1.
+2.
+3.
+
+## Expected/actual behavior
+
+When I follow those steps, I see...
+
+I was expecting to see...
+
+## Isolating the problem
+
+<!-- MARK COMPLETED ITEMS WITH AN [x] -->
+
+- [ ] This bug happens with only WooCommerce plugin active
+- [ ] This bug happens with a default WordPress theme active, or [Storefront](https://woocommerce.com/storefront/)
+- [ ] I can reproduce this bug consistently using the steps above
+
+## WordPress Environment
+
+<details>
+```
+Copy and paste the system status report from **WooCommerce > System Status** in WordPress admin here.
+```
+</details>

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -0,0 +1,34 @@
+---
+name: "\U0001F41E Bug report"
+about: Report a bug if something isn't working as expected in the core WooCommerce
+  plugin.
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is. Please be as descriptive as possible; issues lacking detail, or for any other reason than to report a bug, may be closed without action.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Isolating the problem (mark completed items with an [x]):**
+- [ ] I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
+- [ ] This bug happens with a default WordPress theme active, or [Storefront](https://woocommerce.com/storefront/).
+- [ ] I can reproduce this bug consistently using the steps above.
+
+**WordPress Environment**
+<details>
+```
+Copy and paste the system status report from **WooCommerce > System Status** in WordPress admin.
+```
+</details>

.github/ISSUE_TEMPLATE/Enhancement.md

@@ -0,0 +1,17 @@
+---
+name: "✨ New Enhancement"
+about: "If you have an idea to improve an existing feature in core or need something for development (such as a new hook) please let us know or submit a Pull Request!"
+
+---
+
+**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 what you want to happen.
+
+**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/Feature_request.md

@@ -0,0 +1,17 @@
+---
+name: "\U0001F680 Feature request"
+about: "Suggest a new feature \U0001F389 We'll consider building it if it receives sufficient interest! \U0001F44D"
+
+---
+
+**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 what you want to happen.
+
+**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/Support.md

@@ -0,0 +1,22 @@
+---
+name: "❓ Support Question"
+about: "If you have a question \U0001F4AC please see our docs or use our forums, helpdesk,
+  or Slack Community!"
+
+---
+
+We don't offer technical support on GitHub so we recommend using the following:
+
+**Reading our documentation**
+Usage docs can be found here: https://docs.woocommerce.com/
+
+If you have a problem, you may want to start with the self help guide here: https://docs.woocommerce.com/document/woocommerce-self-service-guide/
+
+**Technical support for premium extensions or if you're a WooCommerce.com customer**
+ from a human being - submit a ticket via the helpdesk
+https://woocommerce.com/contact-us/ 
+
+**General usage and development questions**
+- WooCommerce Slack Community: https://woocommerce.com/community-slack/
+- WordPress.org Forums: https://wordpress.org/support/plugin/woocommerce
+- The WooCommerce Help and Share Facebook group

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,33 @@
+### All Submissions:
+
+* [ ] Have you followed the [WooCommerce Contributing guideline](https://github.com/woocommerce/woocommerce/blob/master/.github/CONTRIBUTING.md)?
+* [ ] Does your code follow the [WordPress' coding standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/)?
+* [ ] Have you checked to ensure there aren't other open [Pull Requests](../../pulls) for the same update/change?
+
+<!-- Mark completed items with an [x] -->
+
+<!-- You can erase any parts of this template not applicable to your Pull Request. -->
+
+### Changes proposed in this Pull Request:
+
+<!-- Describe the changes made to this Pull Request, and the reason for such changes. -->
+
+Closes # .
+
+### How to test the changes in this Pull Request:
+
+1.
+2.
+3.
+
+### Other information:
+
+* [ ] Have you added an explanation of what your changes do and why you'd like us to include them?
+* [ ] Have you written new tests for your changes, as applicable?
+* [ ] Have you successfully ran tests with your changes locally?
+
+<!-- Mark completed items with an [x] -->
+
+### Changelog entry
+
+> Enter a short summary of all changes on this Pull Request. This will appear in the changelog if accepted.