Skip to content
This repository has been archived by the owner on Jan 27, 2021. It is now read-only.

Commit

Permalink
Merge pull request #87 from EYHN/3.0.0-beta.3
Browse files Browse the repository at this point in the history 
3.0.0!!!!!!!!!!!!!!!
  • Loading branch information
@xiazeyu
xiazeyu authored Feb 15, 2018
2 parents 425de96 + fbb662b commit 5a655de
Show file tree
Hide file tree
Showing 575 changed files with 2,153 additions and 25,062 deletions.
209 changes: 209 additions & 0 deletions .eslintrc.js
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,209 @@
module.exports = {
'env': {
'es6': true,
'node': true,
},
// 'extends': 'eslint:all',
'extends': 'eslint:recommended',
'parserOptions': {
'sourceType': 'module',
},
'rules': {
'indent': [
'error',
2
],
'linebreak-style': [
'error',
'unix',
],
'quotes': [
'error',
'single',
],
'semi': [
'error',
'always',
],
'no-console': 'off',
'no-extra-parens': [
'error',
],
'valid-jsdoc': [
'warn',
],
'array-callback-return': [
'error',
],
'block-scoped-var': [
'warn',
],
'consistent-return': [
'error',
{
'treatUndefinedAsUnspecified': true,
}
],
'curly': [
'warn',
'all',
],
'default-case': [
'error',
],
'dot-location': [
'error',
'property',
],
'dot-notation': [
'warn',
],
'eqeqeq': [
'error',
],
'no-else-return': [
'error',
],
'no-empty-function': [
'error',
],
'no-magic-numbers': [
'warn',
{
'ignore': [0],
},
],
'no-multi-spaces': [
'warn',
],
'no-return-assign': [
'error',
],
'no-sequences': [
'warn',
],
'no-useless-concat': [
'error',
],
'no-useless-return': [
'warn',
],
'strict': [
'error',
],
'no-catch-shadow': [
'error',
],
'no-shadow': [
'error',
],
'no-use-before-define': [
'error',
],
'global-require': [
'error',
],
'array-bracket-newline': [
'warn',
],
'array-bracket-spacing': [
'error',
],
'block-spacing': [
'error',
],
'brace-style': [
'error',
],
'camelcase': [
'error',
],
'comma-dangle': [
'error',
'always',
],
'capitalized-comments': [
'warn',
],
'comma-spacing': [
'warn',
],
'comma-style': [
'warn',
],
'eol-last': [
'warn',
],
'func-names': [
'error',
],
'new-parens': [
'error',
],
'no-lonely-if': [
'error',
],
'no-mixed-operators': [
'error',
],
'no-trailing-spaces': [
'error',
],
'no-unneeded-ternary': [
'error',
],
'one-var': [
'error',
'never',
],
'space-before-function-paren': [
'error'
],
'space-before-blocks': [
'error',
],
'space-in-parens': [
'error',
],
'arrow-body-style': [
'error',
],
'arrow-parens': [
'error',
],
'arrow-spacing': [
'error',
],
'no-var': [
'error',
],
'prefer-const': [
'error',
],
'prefer-template': [
'error',
],
'space-infix-ops': [
'error',
],
'space-unary-ops': [
'error',
],
'spaced-comment': [
'error',
],
'quote-props': [
'error',
],
'require-jsdoc': [
'error',
],
'func-style': [
'warn',
'declaration',
],
'padded-blocks': [
'warn',
],
},
};
49 changes: 49 additions & 0 deletions .github/CODE_OF_CONDUCT.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
# 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, gender identity and expression, level of experience, 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 cneyhn@gmail.com or xiazeyu_2011@126.com. The project team will review and investigate all complaints, and will respond in a way that it deems 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 [http://contributor-covenant.org/version/1/4][version]

The second dimension is the best!


[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/
109 changes: 109 additions & 0 deletions .github/CONTRIBUTING.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,109 @@
# Contributing


## Issues

- Most of the time, if this plugin is not working correctly for you it is a simple **configuration** issue.

- **Search on the internet** and **among closed issues** in advance would do a great help for us.

- ~~Please **keep focus on the topic** of any issue, and use **English** as far as possible so that everyone will understand you.~~

- **If you have discovered a bug or have a feature suggestion, feel free to create an issue or pull request on Github.**


## Contributing directly to the source code

**Working on your first Pull Request?** You can learn how from this *free* series
[How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github)

See workflow for more code developing information.


## Submitting Changes

After getting some feedback, push to your fork and submit a pull request. We
may suggest some changes or improvements or alternatives, but for small changes
your pull request should be accepted quickly.

Some things that will increase the chance that your pull request is accepted:

- Follow the existing coding style
- run `npm run lint` before you commit it.
- Write a good commit message use `npm run commit`
- Make sure that your code can work properly.


## Documentation

hexo-helper-live2d's feature is now becoming richer and richer, and documentation is a huge time sink.
We greatly appreciate any time spent fixing typos or clarifying sections in the
documentation.

From opening a bug report to creating a pull request: every contribution is
appreciated and welcome. If you're planning to implement a new feature or change
the api please create an issue first. This way we can ensure that your precious
work is not in vain.



## Workflow: modify the code

- We use **[EditorConfig](http://editorconfig.org/)** to define and maintain consistent coding styles, so have a look first.

- Please use the latest version of Node.js to work with.

### 0. Fork at first

### 1. Install environments

- Use `npm run inst:dev` to **install all the environments**.

### 2. Make changes

- Modify files in the root directory or `/lib`

### 3. Debug until you make sure that your code works properly.

### 4. Commit those changes

- Use `npm run lint` to check your code first.

- Use `git add *`, or choose the file you want to commit.

- We recommend `npm run commit` to commit, **please follow the Angular style**

### 5. Push the changes

- Use `git push` to push the changes to the github server.


## Workflow(author): Release a new version

*Let the Collaborator or author do it.*

### 1. Refresh changelog

- run `npm run changelog`

### 2. Bump the version

- bump the version in `package.json`

- delete `package-lock.json`

- run `npm install` to generate new `package-lock.json`

### 3. Commit files

### 4. Tag and release a new version

- In the Github page.

### 5. Update changelog again

- Use `npm run changelog`, and commit it.

### 6. Publish the package to npm.

- Use `npm publish` to publish it.
15 changes: 15 additions & 0 deletions .github/ISSUE_TEMPLATE.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
### Expected behavior 预期行为

### Actual behavior 实际行为

### Steps to reproduce the behavior 复现步骤


- [ ] I have alreday read instructions in [CONTRIBUTING](./CONTRIBUTING.md).
我已仔细阅读[CONTRIBUTING](./CONTRIBUTING.md)中的相关内容。

> Change the `[ ]` into `[x]` to show your acceptance.
将 `[ ]` 变为 `[x]` 来表示你接受了这些问题。


@EYHN @xiazeyu
Loading

0 comments on commit 5a655de

Please sign in to comment.