Skip to content
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

Improvements + updates โœจ #43

Open
wants to merge 21 commits into
base: master
Choose a base branch
from

Conversation

3imed-jaberi
Copy link
Member

  • update .gitignore file ๐Ÿž ..
  • avoid generating package-lock.json โ˜”๏ธ ..
  • use xo over native eslint to lint ๐Ÿ’…๐Ÿป ..
  • update LICENSE ๐Ÿ— ..
  • use nyc over istanbul for coverage ๐Ÿ’ฏ ..
  • update mocha โ˜•๏ธ ..
  • update test code (support koa 1 and 2 + use koa-convert to switch) ๐Ÿงช ..
  • update ci pipeline ๐ŸŽฒ ..
  • remove some files โŒ ..
  • improve the source code โœจ ..
  • update README.md ( add some note + add one line of code) ๐Ÿ“‹ ..
  • better pkg.json ๐ŸŽ— ..

ready to next release ๐Ÿš€ ..

@codecov
Copy link

codecov bot commented Jun 11, 2020

Codecov Report

Merging #43 into master will increase coverage by 0.35%.
The diff coverage is 97.36%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #43      +/-   ##
==========================================
+ Coverage   98.20%   98.56%   +0.35%     
==========================================
  Files           1        1              
  Lines         167      139      -28     
  Branches       35        0      -35     
==========================================
- Hits          164      137      -27     
+ Misses          3        2       -1     
Impacted Files Coverage ฮ”
index.js 98.56% <97.36%> (+0.35%) โฌ†๏ธ

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 ca9d0f9...2a14b95. Read the comment docs.

@3imed-jaberi
Copy link
Member Author

@niftylettuce, kindly bro can you merge this PR then #45 and publish new version and close this issue #46

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.

1 participant