Closed germanattanasio closed 5 years ago
Is ignoring compiled files a standard practice in node-sdk?
It makes it impossible to install this library from branch because I get no src/
and no lib/
.
How am I supposed to test my changes now? I would rather remove package-lock.json from git, because this is a library, so lock file doesn't matter.
@Naktibalda I added back the lib
files so that you can test this from github.
:exclamation: No coverage uploaded for pull request base (
botkit-next@9ac00a3
). Click here to learn what that means. The diff coverage is78.57%
.
@@ Coverage Diff @@
## botkit-next #179 +/- ##
=============================================
Coverage ? 78.5%
=============================================
Files ? 2
Lines ? 107
Branches ? 22
=============================================
Hits ? 84
Misses ? 19
Partials ? 4
Impacted Files | Coverage Δ | |
---|---|---|
lib/utils.js | 100% <ø> (ø) |
|
lib/index.js | 65.15% <78.57%> (ø) |
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 9ac00a3...47c18b5. Read the comment docs.
:tada: This PR is included in version 2.0.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
@Naktibalda I did some updates to your code to update the tests to use typescript and cleanup extra code that we had for when we were using plain javascript.
src
andlib
is ignore from the repository.lib
with the types and javascript but notsrc
with the typescript.simple-bot
was updatedmulti-bot
was not updated as I ran out of time 😞jest
and addedcodecov
for code coverageWhat I need.
---- for semantic versioning ---
BREAKING CHANGE: