diff --git a/.babelrc b/.babelrc deleted file mode 100644 index 45b8019..0000000 --- a/.babelrc +++ /dev/null @@ -1,23 +0,0 @@ -{ - presets: [ - ['env', { - modules: false, - targets: { - browsers: [ - '> 1%', - 'last 1 versions', - 'last 4 Android versions', - 'last 3 iOS versions' - ] - } - }], - 'stage-2' - ], - plugins: ['transform-runtime'], - env: { - test: { - presets: ['env', 'stage-2'], - plugins: ['istanbul'] - } - } -} diff --git a/.editorconfig b/.editorconfig index b421fce..4146897 100644 --- a/.editorconfig +++ b/.editorconfig @@ -9,4 +9,4 @@ trim_trailing_whitespace = true insert_final_newline = true [*.md] -trim_trailing_whitespace = false \ No newline at end of file +trim_trailing_whitespace = false diff --git a/.eslintignore b/.eslintignore deleted file mode 100644 index 853251d..0000000 --- a/.eslintignore +++ /dev/null @@ -1,3 +0,0 @@ -/karma.conf.js -/webpack.config.js -/dist/*.js diff --git a/.eslintrc.yml b/.eslintrc.yml deleted file mode 100644 index 601f218..0000000 --- a/.eslintrc.yml +++ /dev/null @@ -1,24 +0,0 @@ ---- - root: true - extends: airbnb-base - parser: babel-eslint - parserOptions: - ecmaVersion: 6 - sourceType: module - ecmaFeatures: - impliedStrict: true - env: - browser: true - plugins: - - html - settings: - import/resolver: - webpack: - config: ./webpack.config.js - rules: - import/extensions: - - error - - always - - - js: never - vue: never diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..dc54ab1 --- /dev/null +++ b/.github/CODE_OF_CONDUCT.md @@ -0,0 +1,73 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, 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. + +## Our Standards + +Examples of behavior that contributes to creating a positive environment +include: + +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +* The use of sexualized language or imagery and unwelcome sexual attention or + advances +* Trolling, insulting/derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or electronic + address, without explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Our Responsibilities + +Project maintainers are responsible for clarifying the standards of acceptable +behavior and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behavior. + +Project maintainers 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, or to ban temporarily or +permanently any contributor for other behaviors that they deem inappropriate, +threatening, offensive, or harmful. + +## Scope + +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. Examples of +representing a project or community include using an official project e-mail +address, posting via an official social media account, or acting as an appointed +representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported by contacting the project team at [scdzwyxst@gmail.com](mailto:scdzwyxst@gmail.com). All +complaints will be reviewed and investigated and will result in a response that +is deemed necessary and appropriate to the circumstances. The project team is +obligated to maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good +faith may face temporary or permanent repercussions as determined by other +members of the project's leadership. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html + +[homepage]: https://www.contributor-covenant.org diff --git a/.github/COMMIT_CONVENTION.md b/.github/COMMIT_CONVENTION.md new file mode 100644 index 0000000..ccd11a6 --- /dev/null +++ b/.github/COMMIT_CONVENTION.md @@ -0,0 +1,91 @@ +## Git Commit Message Convention + +> This is adapted from [Angular's commit convention](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular). + +#### TL;DR: + +Messages must be matched by the following regex: + +``` js +/^(revert: )?(build|chore|ci|docs|feat|fix|perf|refactor|style|test)(\((core|config|spinner|deps)\))?: .{1,72}$/ +``` + +#### Examples + +Appears under "Features" header, `core` subheader: + +``` +feat(core): support top direction +``` + +Appears under "Bug Fixes" header, `spinner` subheader, with a link to issue #28: + +``` +fix(spinner): animation compatibility + +close #28 +``` + +Appears under "Performance Improvements" header, and under "Breaking Changes" with the breaking change explanation: + +``` +perf(core): use @infinite event instead of on-infinite property + +BREAKING CHANGE: The 'on-infinite' property has been removed. +``` + +The following commit and commit `a88ffb7` do not appear in the changelog if they are under the same release. If not, the revert commit appears under the "Reverts" header. + +``` +revert: feat(core): support top direction + +This reverts commit a88ffb776878a07cb2f349bc3dd8cce59932b7e1. +``` + +### Full Message Format + +A commit message consists of a **header**, **body** and **footer**. The header has a **type**, **scope** and **subject**: + +``` +(): + + + +