Skip to content

Commit b46b496

Browse files
janryWangjanryWang
committed
refactor(project): first commit
Initialize the project, the code is currently unavailable.
0 parents  commit b46b496

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

107 files changed

+9709
-0
lines changed

‎.babelrc

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
{
2+
"presets": [["@babel/preset-env", { "loose": true }], "@babel/preset-react"],
3+
"plugins": [
4+
"@babel/plugin-proposal-class-properties",
5+
"@babel/plugin-syntax-dynamic-import",
6+
["@babel/plugin-proposal-decorators", { "legacy": true }]
7+
]
8+
}

‎.editorconfig

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# EditorConfig is awesome: http://EditorConfig.org
2+
3+
# top-most EditorConfig file
4+
root = true
5+
6+
# Unix-style newlines with a newline ending every file
7+
[*]
8+
end_of_line = lf
9+
insert_final_newline = true
10+
indent_style = space
11+
indent_size = 2
12+
13+
[*.gradle]
14+
indent_size = 4

‎.eslintignore

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
node_modules
2+
lib
3+
dist
4+
build
5+
coverage
6+
expected
7+
website
8+
gh-pages
9+
weex

‎.eslintrc

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
{
2+
"parser": "babel-eslint",
3+
"extends": ["standard", "standard-react"],
4+
"env": {
5+
"es6": true
6+
},
7+
"settings": {
8+
"react": {
9+
"version": "16.8.2"
10+
}
11+
},
12+
"plugins": ["react", "react-hooks"],
13+
"parserOptions": {
14+
"ecmaVersion": 6,
15+
"sourceType": "module",
16+
"ecmaFeatures": {
17+
"jsx": true
18+
}
19+
},
20+
"rules": {
21+
// don't force es6 functions to include space before paren
22+
"space-before-function-paren": 0,
23+
"react/prop-types": 0,
24+
// allow specifying true explicitly for boolean props
25+
"react/jsx-boolean-value": 0,
26+
"react-hooks/rules-of-hooks": "error",
27+
"react/no-did-update-set-state": 0
28+
}
29+
}

‎.github/CONTRIBUTING.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# Contributing Guide
2+
3+
Hi! I’m really excited that you are interested in contributing to Rax. Before submitting your contribution though, please make sure to take a moment and read through the following guidelines.
4+
5+
- [Issue Reporting Guidelines](#issue-reporting-guidelines)
6+
- [Pull Request Guidelines](#pull-request-guidelines)
7+
- [Git Commit Specific](./GIT_COMMIT_SPECIFIC.md)
8+
9+
10+
## Issue Reporting Guidelines
11+
12+
- The issue list of this repo is **exclusively** for bug reports and feature requests. Non-conforming issues will be closed immediately.
13+
14+
- For simple beginner questions, you can get quick answers from
15+
16+
- For more complicated questions, you can use Google or StackOverflow. Make sure to provide enough information when asking your questions - this makes it easier for others to help you!
17+
18+
- Try to search for your issue, it may have already been answered or even fixed in the development branch.
19+
20+
- Check if the issue is reproducible with the latest stable version of Rax. If you are using a pre-release, please indicate the specific version you are using.
21+
22+
- It is **required** that you clearly describe the steps necessary to reproduce the issue you are running into. Issues with no clear repro steps will not be triaged. If an issue labeled "need repro" receives no further input from the issue author for more than 5 days, it will be closed.
23+
24+
- For bugs that involves build setups, you can create a reproduction repository with steps in the README.
25+
26+
- If your issue is resolved but still open, don’t hesitate to close it. In case you found a solution by yourself, it could be helpful to explain how you fixed it.
27+
28+
## Pull Request Guidelines
29+
30+
- Only code that's ready for release should be committed to the master branch. All development should be done in dedicated branches.
31+
- Checkout a **new** topic branch from master branch, and merge back against master branch.
32+
- Work in the `src` folder and **DO NOT** checkin `dist` in the commits.
33+
- Make sure `npm test` passes.
34+
- If adding new feature:
35+
- Add accompanying test case.
36+
- Provide convincing reason to add this feature. Ideally you should open a suggestion issue first and have it greenlighted before working on it.
37+
- If fixing a bug:
38+
- If you are resolving a special issue, add `(fix #xxxx[,#xxx])` (#xxxx is the issue id) in your PR title for a better release log, e.g. `update entities encoding/decoding (fix #3899)`.
39+
- Provide detailed description of the bug in the PR. Live demo preferred.
40+
- Add appropriate test coverage if applicable.
41+
42+
43+
## Git Commit Specific
44+
45+
- Your commits message must follow our [git commit specific](./GIT_COMMIT_SPECIFIC.md).
46+
- We will check your commit message, if it does not conform to the specification, the commit will be automatically refused, make sure you have read the specification above.
47+
- You could use `git cz` with a CLI interface to replace `git commit` command, it will help you to build a proper commit-message, see [commitizen](https://github.com/commitizen/cz-cli).
48+
- It's OK to have multiple small commits as you work on your branch - we will let GitHub automatically squash it before merging.

‎.github/GIT_COMMIT_SPECIFIC.md

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
# GIT COMMIT MESSAGE CHEAT SHEET
2+
3+
**Proposed format of the commit message**
4+
5+
```
6+
<type>(<scope>): <subject>
7+
8+
<body>
9+
```
10+
11+
All lines are wrapped at 100 characters !
12+
13+
14+
**Allowed `<type>`**
15+
16+
- feat (A new feature)
17+
- fix (A bug fix)
18+
- docs (Documentation only changes)
19+
- style (Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc))
20+
- perf (A code change that improves performance)
21+
- refactor (A code change that neither fixes a bug nor adds a feature)
22+
- test (Adding missing tests or correcting existing tests)
23+
- build (Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm))
24+
- ci (Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs))
25+
- chore (Other changes that don't modify src or test files)
26+
- revert (Reverts a previous commit)
27+
28+
**Allowed `<scope>`**
29+
Scope could be anything specifying place of the commit change.
30+
31+
For example $location, $browser, compiler, scope, ng:href, etc...
32+
33+
34+
**Breaking changes**
35+
All breaking changes have to be mentioned in message body, on separated line:
36+
​ _Breaks removed $browser.setUrl() method (use $browser.url(newUrl))_
37+
​ _Breaks ng: repeat option is no longer supported on selects (use ng:options)_
38+
39+
40+
**Message body**
41+
42+
- uses the imperative, present tense: “change” not “changed” nor “changes”
43+
- includes motivation for the change and contrasts with previous behavior

‎.github/ISSUE_TEMPLATE.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
## Help us to manage our issues by answering the following:
2+
3+
1. How would you tag this issue?
4+
5+
- Question
6+
- Bug
7+
- Discussion
8+
- Feature request
9+
- Tip
10+
- Enhancement
11+
- Performance
12+
13+
2. Describe your issue:
14+
15+
- What is the current behavior?
16+
- What is the expected behavior?
17+
- Which versions of Rax, and which browser / OS are affected by this issue?
18+
- Did this work in previous versions of Rax?
19+
20+
3. If your issue is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via [Bug Report Template](http://codepen.io/taobaofed/pen/oByQGb) on CodePen
21+
.

‎.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
*Before* submitting a pull request, please make sure the following is done...
2+
3+
1. Fork the repo and create your branch from `master`.
4+
2. If you've added code that should be tested, add tests!
5+
3. If you've changed APIs, update the documentation.
6+
4. Ensure the test suite passes (`npm test`).
7+
5. Make sure your code lints (`npm run lint`) - we've done our best to make sure these rules match our internal linting guidelines.

‎.gitignore

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
*~
2+
*.swp
3+
.DS_Store
4+
npm-debug.log
5+
lerna-debug.log
6+
npm-debug.log*
7+
lib/
8+
dist/
9+
build/
10+
coverage/
11+
node_modules/
12+
examples/test
13+
.idea/

‎.npmrc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
package-lock=false

0 commit comments

Comments
 (0)