lib: handle when report severity is not set#765
Merged
RafaelGSS merged 1 commit intonodejs:mainfrom Jan 2, 2024
Merged
Conversation
RafaelGSS
force-pushed
the
handle-no-severity-report
branch
from
f1e0b2a to
26b3969
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #765 +/- ##
=======================================
Coverage 82.97% 82.97%
=======================================
Files 37 37
Lines 4200 4200
=======================================
Hits 3485 3485
Misses 715 715 ☔ View full report in Codecov by Sentry. |
aduh95
approved these changes
Jan 2, 2024
RafaelGSS
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Ref: https://github.com/nodejs-private/node-private/issues/514