-
Notifications
You must be signed in to change notification settings - Fork 67
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
logging for conflicting url paths #718
Conversation
f14d4bb
to
699e6af
Compare
699e6af
to
c1b2eec
Compare
|
||
// Error returns the error string | ||
func (e *urlFailure) Error() string { | ||
return fmt.Sprintf("panic: path: %q method: %q conflicts with an existing path", e.url, e.method) |
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.
don't think panic
should be part of the message itself.
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.
acked. we can improve message in future diff.
…er gives this lower coverage error
@@ -128,7 +128,7 @@ cat ./coverage/istanbul.json | jq '[ | |||
] | from_entries' > ./coverage/istanbul-runtime.json | |||
|
|||
echo "Checking code coverage for runtime folder" | |||
./node_modules/.bin/istanbul check-coverage --statements 99.92 \ | |||
./node_modules/.bin/istanbul check-coverage --statements 99.85 \ |
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'm sure there are tests for duplicate URL case, I would have not expected the coverage to drop. If this is not the case, we should add coverage instead of changing this.
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.
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.
and see the previous run of this, where test fails and you can see it didn't decrease for this package.
* logging for conflicting url paths * coverage didnt increase for affected path, however touching this folder gives this lower coverage error
No description provided.