Skip to content

Use throttle instead of debounce (with rollback changes of dist file) #163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Jul 12, 2018

Conversation

chanzxxx
Copy link
Contributor

#161 with original dist file

@codecov
Copy link

codecov bot commented Jul 11, 2018

Codecov Report

Merging #163 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #163   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           2      2           
  Lines          92     95    +3     
  Branches       24     25    +1     
=====================================
+ Hits           92     95    +3
Impacted Files Coverage Δ
src/components/InfiniteLoading.vue 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 24aeeab...eace9cc. Read the comment docs.

@chanzxxx chanzxxx changed the title Use throttle instead of debounce Use throttle instead of debounce (with rollback changes of dist file) Jul 11, 2018
@PeachScript PeachScript merged commit 299999d into PeachScript:master Jul 12, 2018
@PeachScript
Copy link
Owner

@whdckszxxx thanks! You can append to the existing PR in the next time, without open a new one.

Best regards.

@chanzxxx
Copy link
Contributor Author

@PeachScript I was new to PR :) I will do that way next time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants