Skip to content
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

Allow calling Bugsnag.notify() with no arguments #197

Merged
merged 4 commits into from Oct 6, 2016

Conversation

foxyblocks
Copy link

fixes #196

@snmaynard
Copy link
Contributor

I think we should actually notify in this case

@foxyblocks
Copy link
Author

Should we just send "Bugsnag.notify() called with no arguments" as the name?

@snmaynard
Copy link
Contributor

as the message maybe. Can we put something like BugsnagError as the class?

@foxyblocks foxyblocks changed the title Ignore calls to Bugsnag.notify() with no arguments Allow calling Bugsnag.notify() with no arguments Oct 5, 2016
@@ -115,6 +118,12 @@
// Notify Bugsnag about an error by passing in a `name` and `message`,
// without requiring an exception.
self.notify = function (name, message, metaData, severity) {
if (!name) {
name = "UnspecifiedBugsnagError";

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be worth pulling this to the top of the file where we declare some other constant-esque variables?

@eanakashima
Copy link

👍 Looks good! One thought: since this is a manual call to Bugsnag.notify, maybe the error class doesn't need to have "Error" in it? A class name like BugsnagNotify might get closer to suggesting the typical severity.

@foxyblocks foxyblocks merged commit 9ceeb65 into master Oct 6, 2016
@foxyblocks foxyblocks deleted the check-notify-arguments branch October 6, 2016 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants