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
fix(framework-core): combine review comments #116
fix(framework-core): combine review comments #116
Conversation
Codecov Report
@@ Coverage Diff @@
## comment-pr #116 +/- ##
==============================================
+ Coverage 91.85% 91.87% +0.02%
==============================================
Files 26 25 -1
Lines 2332 2289 -43
Branches 164 161 -3
==============================================
- Hits 2142 2103 -39
+ Misses 189 185 -4
Partials 1 1
Continue to review full report at Codecov.
|
} | ||
const errorMessage = buildErrorMessage(outOfScopeSuggestions); | ||
if (errorMessage) { | ||
logger.warn('Some suggestions could not be made'); |
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.
I think we're missing the case of no suggestion and no errors (which should do nothing).
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.
Hm wouldn't it be the case: when we have no suggestions we would still want to comment that out of scope suggestions were generated?
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.
I propose we should do nothing if we have both no suggestions to make and no out of scope suggestions generated (assuming users care about all suggestions generated). Do you agree?
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.
Correct, if there are no suggestions and no errors, we should do nothing.
…n pull requests (#105) * feat(patch text to hunk bounds): support regex for patch texts (#83) * fix(patch text to hunk bounds): support regex for patch texts * more comments and more tests * fix(framework-core): core-library get remote patch ranges (#84) * fix(framework-core): given files old content and new content, compute the valid hunks (#86) * fix(framework-core): parse raw changes to ranges * refactor(framework-core): rename modules, functions, & re-org project structure (#89) * fix(framework-core): hunk to patch object (#91) * feat: build failure message from invalid hunks (#90) * test: add failing stub and test for building the failure message * fix: implement message building * fix: use original line numbers in error message * docs: add docstring * docs: add note about empty input returning empty string * feat(framework-core): comment on prs given suggestions (#93) * feat(framework-core): main interface for create review on a pull request (#114) * feat(framework-core): main interface for create review on a pull request * docs: fix typo * nits and typos... * gts lint warning fix * fix(framework-core): combine review comments (#116) * fix(framework-core): collapsing timeline and inline comments into single review * test: fixed imports * added case when there are out of scope suggestions and no valid suggestions * feat(framework-core): return review number and variable renaming (#117) * feat(framework-core): return review number and variable renaming * lint Co-authored-by: Jeff Ching <chingor@google.com> Co-authored-by: Justin Beckwith <justin.beckwith@gmail.com> Co-authored-by: Benjamin E. Coe <bencoe@google.com>
Collapses timeline and inline comment into a single pull request. This also prompted some refactoring because of the sequence of events change.
Addresses review comment
Towards #105