Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Bring project back to life #26
Bring project back to life #26
Changes from all commits
b636f6f
581289d
f9592a3
499e912
f51ec9a
ae66f0a
161b8c3
fc0aa8d
7c2bbb9
5d63386
b3f44f4
28cd4ba
3d73390
62aeaaa
e439c47
781a34c
ac176d8
2f5ee31
d72e0c8
b931f91
9964bf5
951d22c
ad55f4e
2a0f0db
cdd4f12
6eff286
eedffa3
01d33e1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
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.
If this change was to fix non passing tests, let's try and fix the tests later so we get 100 coverage as the only thing I actually want to test is this package's API and all permutations of using the API. I don't want to have tests of implementation details.
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.
It was not my aim to fix test passing but 100% coverage is something that sometimes cannot be possible at all
A coverage of 85%-95% is totally valid
Lines like https://github.com/linterjs/core/blob/master/src/errors.ts#L4-L7 wont be covered (currently) 🤔
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.
Using ~ will only allow PATCH version updates, while ^ will allow MINOR version updates. I guess I'm ok with only allowing PATCH updates, however if this package will be using
@linter/cli
in the future that will have to be using ^ as our packages will never have changes to PATCH as that will always be 0.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 sorry! you are right, but only for
dependencies
.But we should use ~ for
devDependencies
I'm always using ~ but I'm using them in frontend projects, and these are not dependencies for other projects ^^
This file was deleted.
This file was deleted.