Skip to content

Commit

Permalink
4.6.1 (#35)
Browse files Browse the repository at this point in the history
* refactor: code structure

* tweak: readme

* tweak: demo style

* tweak: readme

* fix: rail's borderradius cannot be dynamiclly set

* tweak: dynamically set data

* fix: internalscrollTop should default to 0

* tweak: the position of preventDefault options in global-config.js

* perf(touch): optimize scroll experience

* tweak: readme

* buid: release 4.5.13

* changelog

* chore: format code with prettier

* tweak: manully add height or width to vuescroll elm  when mounted

* build: release 4.5.14
Feature:
  Add sizeStrategy option for vuescroll  To decide use a numberic size  or
  a percent size for vuescroll while parent dom's size maybe a numberic
  value or a percent value
close #26

* build: release 4.5.15
Hot Fix:
Vuescroll's width and height should default to `100%` in case of getting
an  incorrect size in slide mode .

* tweak: bar/rail width/height default from 5px to  6px

* tweak: readme.md
WIP: refactor unit test module

* tweak: readme
WIP: refactor unit test module

* chore: add unit test

* tweak: ci

* tweak: ci

* tweak: ci

* tweak: ci

* build: release 4.5.16
chore:
add unit test
fix:
window onresize may throw an error

* fix: typo

* fix: rename comonent to component

* tweak: readme

* chore: delete useless files

* tweak: Supplement Readme

* tweak: readme

* tweak: readme

* tweak: readme

* tweak: readme

* tweak: readme

* tweak: readme

* tweak: readme

* tweak: readme

* tweak: readme

* tweak: readme

* tweak: inspired link in readme

* tweak: readme

* tweak: image in readme

* tweak: readme-zh

* tweak: readme

* feat(api): Add scrollIntoView api that allows you scroll an elment into view

* build: 4.5.17

* changelog

* tweak: readme

* tweak

* tweak

* tweak

* tweak

* tweak readme

* update inspire

* fix: get incorrect hash when component mounted

* build: 4.5.18

* changelog

* chore: tweak indent

* fix: incorrect bar position when there is a error of scrollHeight in browser

* chore: fix broken demo link

* chore: strip license ext

* perf(scrollbar): make the position of scrollbar more accurate

* build: 4.5.19

* chore: changelog

* 4.5.20

* fix: update bar when mouse enters or moves

* build: 4.5.21

* changelog

* chore: tweak the intro of vuescroll in readme

* perf(bar): refactor bar and rail

* build: 4.5.22

* chore: changelog

* chore: delete deprecated config

* build: 4.5.23
fix: Vuescroll cannot detect scroll  when parent dom's size is not a fixed value
(#29)

* chore: changelog

* chore: fix typo

* tweaks: readme

* feat(bar): support dragging in mobile

* build: 4.5.24

* chore: changelog

* build: 4.5.25
tweaks:
Wrap `isSupportTouch` by a function to pass ssr exam

* build: 4.5.26
tweaks: Call e.preventDefault when dragging the bar.

* feat(bar): Add showDuration to controll the show time of bars

* fix(silde-mode): what scroll-panel's display style is inline-block  may
disrupt content style (@30)

* fix(silde-mode): what scroll-panel's display style is inline-block  may
disrupt content style (#30)

* buid: 4.5.27

* chore:changelog

* teeaks: changelog

* tweaks: readme

* tweak: readme

* tweak: readme

* fix: typo in createPanel.js

* feat: Support customize svg in pull-refresh or push-load

* build: 4.5.29

* chore: changelog

* chore: changelog

* fix: The content height while push-load is enable

* build:4.5.30

* chore: changelog

* tweak: set 100% when vbar's size is 0

* update issue templates

* fix: add min-width to scrollPanel, scrollContent(#32)

* build: 4.5.31

* chore: changelog

* fix lint

* fix: update bar in setTimeout (#31)

* feat(api): add triggerRefreshOrLoad Api that you can trigger refresh or load directly

* build: 4.5.32

* changelog

* chore: wx.png

* fix typo

* fix: don't call complete while __isDecelerating is false

* feat: add `direction info for event handle`

* build: 4.5.23

* chore: changelog

* tweaks readme

* chore: change website address

* tweak: readme

* chore: tweak shields address

* tweak: readme (#34)

* fix: add z-index to rail

* build: 4.6.0

* chore: changelog

* feat: add border-radius to rail

* 4.6.1
  • Loading branch information
wangyi7099 authored Jun 5, 2018
1 parent 057dfda commit a8f25b3
Show file tree
Hide file tree
Showing 75 changed files with 8,594 additions and 6,008 deletions.
16 changes: 13 additions & 3 deletions .circleci/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -40,11 +40,21 @@ jobs:
if [[ -z $CI_PULL_REQUEST ]]; then
cat ./test/coverage/lcov.info | ./node_modules/.bin/codecov
fi
lint:
<<: *defaults
steps:
- attach_workspace:
at: ~/project
# run tests!
- run: npm run lint
workflows:
version: 2
install-and-parallel-test:
jobs:
- install
# - test-cover:
# requires:
# - install
- test-cover:
requires:
- install
- lint:
requires:
- install
3 changes: 2 additions & 1 deletion .eslintignore
Original file line number Diff line number Diff line change
@@ -1 +1,2 @@
dist
dist
coverage
31 changes: 19 additions & 12 deletions .eslintrc.js
Original file line number Diff line number Diff line change
@@ -1,19 +1,26 @@
module.exports = {
root: true,
"extends": "eslint:recommended",
extends: 'eslint:recommended',
rules: {
indent: ['error', 2, { MemberExpression: 'off' }],
"semi": ["error", "always"],
"no-undef": 0,
"quotes": ["error", "double"],
"excludedFiles": "dist/*.js",
semi: ['error', 'always'],
'no-undef': 0,
'no-unused-vars': [
'error',
{
argsIgnorePattern: '^h$'
}
],
quotes: ['error', 'single'],
excludedFiles: 'dist/*.js'.anchor,
'no-console': [0]
},
"parserOptions": {
"ecmaVersion": 6,
"sourceType": "module",
"ecmaFeatures": {
"jsx": true,
"experimentalObjectRestSpread": true
parserOptions: {
ecmaVersion: 6,
sourceType: 'module',
ecmaFeatures: {
jsx: true,
experimentalObjectRestSpread: true
}
}
}
};
13 changes: 13 additions & 0 deletions .github/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# Contributor Code of Conduct

As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, age, or religion.

Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.

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. Project maintainers who do not follow the Code of Conduct may be removed from the project team.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.

This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.0.0, available at [http://contributor-covenant.org/version/1/0/0/](http://contributor-covenant.org/version/1/0/0/)
91 changes: 91 additions & 0 deletions .github/COMMIT_CONVENTION.md
Original file line number Diff line number Diff line change
@@ -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: )?(feat|fix|polish|docs|style|refactor|perf|test|workflow|ci|chore|types)(\(.+\))?: .{1,50}/
```

#### Examples

Appears under "Features" header, `compiler` subheader:

```
feat(compiler): add 'comments' option
```

Appears under "Bug Fixes" header, `v-model` subheader, with a link to issue #28:

```
fix(v-model): handle events on blur
close #28
```

Appears under "Performance Improvements" header, and under "Breaking Changes" with the breaking change explanation:

```
perf(core): improve vdom diffing by removing 'foo' option
BREAKING CHANGE: The 'foo' option has been removed.
```

The following commit and commit `667ecc1` 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(compiler): add 'comments' option
This reverts commit 667ecc1654a317a13331b17617d973392f415f02.
```

### Full Message Format

A commit message consists of a **header**, **body** and **footer**. The header has a **type**, **scope** and **subject**:

```
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
```

The **header** is mandatory and the **scope** of the header is optional.

### Revert

If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.

### Type

If the prefix is `feat`, `fix` or `perf`, it will appear in the changelog. However if there is any [BREAKING CHANGE](#footer), the commit will always appear in the changelog.

Other prefixes are up to your discretion. Suggested prefixes are `docs`, `chore`, `style`, `refactor`, and `test` for non-changelog related tasks.

### Scope

The scope could be anything specifying place of the commit change. For example `core`, `compiler`, `ssr`, `v-model`, `transition` etc...

### Subject

The subject contains succinct description of the change:

* use the imperative, present tense: "change" not "changed" nor "changes"
* don't capitalize first letter
* no dot (.) at the end

### Body

Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
The body should include the motivation for the change and contrast this with previous behavior.

### Footer

The footer should contain any information about **Breaking Changes** and is also the place to
reference GitHub issues that this commit **Closes**.

**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
58 changes: 58 additions & 0 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
# English Version

Contributing code from two aspects:

### Code level

Vuescroll is extremely easy to expand.You only have to do 2 steps

1. To modify / add the corresponding features at the corresponding modules in the [global-config.js](https://github.com/YvesCoding/blob/dev/src/shared/global-config.js) file, for example, I want to add a feature that can configure the color of the scrolling panel, the default is red, as follows:
![](https://github.com/wangyi7099/pictureCdn/blob/master/allPic/vuescroll/s1.jpg?raw=true)
2. Find the corresponding module file and modify it in the corresponding code of the module, as follows:
![](https://github.com/wangyi7099/pictureCdn/blob/master/allPic/vuescroll/s2.jpg?raw=true)
<br>
![](https://github.com/wangyi7099/pictureCdn/blob/master/allPic/vuescroll/s3.jpg?raw=true)

### Git level

1. Fork this repo.
2. Clone the repo you have just forked.

```base
git clone [email protected]:<Your Username>/vuescroll.git
```

3. Modify the code in your local and push the code to your remote repo(Commit messages should follow the [commit message convention](./COMMIT_CONVENTION.md) so that changelogs can be automatically generated).
4. Click `New pull request` in vuescroll repo as follows:
<br /><img src="https://github.com/wangyi7099/pictureCdn/blob/master/allPic/others/pr.jpg?raw=true" />
5. When I agree, your code will merge into the `dev` branch!

# 中文版本

从两方面贡献代码:

### 代码层面

Vuescroll 是极其容易扩展的,你基本只需要做 2 步即可。

1.[global-config.js](https://github.com/YvesCoding/blob/dev/src/shared/global-config.js) 文件中对应的模块处修改/增加对应的特性,比如,我想增加一个可以配置滚动面板颜色的特性,默认是红色,如下图:
<br>
![](https://github.com/wangyi7099/pictureCdn/blob/master/allPic/vuescroll/s1.jpg?raw=true)
2. 找到对应的模块文件, 并在模块的对应的代码处修改即可,如下图:
<br>
![](https://github.com/wangyi7099/pictureCdn/blob/master/allPic/vuescroll/s2.jpg?raw=true)
<br>
![](https://github.com/wangyi7099/pictureCdn/blob/master/allPic/vuescroll/s3.jpg?raw=true)

### Git 层面

1. 把这个项目 fork 下来。
2. 把你的 fork 的项目克隆下来

```base
git clone [email protected]:<Your Usernmae>/vuescroll.git
```

3. 在你的本地修改代码然后 push 到你的远程仓库(提交消息应该遵循[[commit message convention](./COMMIT_CONVENTION.md) 以便能自动生成changelog)
4. 在 vuescroll 项目地址点击`New pull request`,如下图所示:<br /><img src="https://github.com/wangyi7099/pictureCdn/blob/master/allPic/others/pr.jpg?raw=true" />
5. 等我点击同意, 你的代码就会被 merge 到`dev`分支了!
30 changes: 30 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
name: Bug report
about: Create a report to help us improve

---

<!-- Before submmitting a bug, make sure that you have read the documentation and the general FAQ in the readme. -->

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Browser (please complete the following information):**
[e.g. chrome, safari]
- Version [e.g. 22]

**Additional context**
Add any other context about the problem here.
17 changes: 17 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
name: Feature request
about: Suggest an idea for this 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 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.
3 changes: 2 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,5 @@ server.js
compress.js
coverage
test.html
package-lock.json
package-lock.json
debug.log
Loading

0 comments on commit a8f25b3

Please sign in to comment.