-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
feat: support inner not, not in simple types #61
Conversation
Codecov Report
@@ Coverage Diff @@
## master #61 +/- ##
==========================================
- Coverage 98.12% 97.56% -0.57%
==========================================
Files 5 6 +1
Lines 639 697 +58
Branches 267 298 +31
==========================================
+ Hits 627 680 +53
- Misses 12 15 +3
- Partials 0 2 +2
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job, let's avoid here logic for not
and do this on other PR?
what is problem with CI? coverage decrease? |
Yep, don't know why, you can ignore this |
@evilebottnawi I suggest to split |
@evilebottnawi I think this is ready to review 😁 |
@evilebottnawi I can do it, but later. Busy right now. |
@vankop great |
# Conflicts: # src/ValidationError.js # test/__snapshots__/index.test.js.snap
@vankop let's wait a bit with this, at the moment I'm adding JSDoc for all project and continue after this 👍 |
TypeScript 🤩🤗 |
/cc @vankop we can continue development too 😄 |
# Conflicts: # src/ValidationError.js # test/__snapshots__/index.test.js.snap # test/index.test.js
# Conflicts: # src/ValidationError.js # test/__snapshots__/index.test.js.snap
npm audit fix npm audit fix one more
@evilebottnawi so much work is done =) need rereview |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, a lot of changes, very hard to review, maybe we can separate this PR on parts? Also it will be good for git history?
@vankop friendly ping |
# Conflicts: # package-lock.json
I will try to reduce |
Will be great, anyway thanks for a job, if you can't reduce ping me and I will try to review this big PR |
This PR contains a:
Motivation / Use-Case
fixes #65
#42
part of 1st proposal.
Breaking Changes
no
Additional Info
Nothing