-
Notifications
You must be signed in to change notification settings - Fork 94
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
Throw error if null or undefined #65
base: master
Are you sure you want to change the base?
Conversation
@@ -10,7 +10,7 @@ function symbols(code) { | |||
} | |||
|
|||
function slug(string, opts) { | |||
string = string.toString(); | |||
string = (string || '').toString(); |
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.
Maybe it would be more semantic to just have the function return null or undefined if the string is null or undefined?
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.
In my opinion, null
and undefined
should be considered a developer mistake and throw.
if (string === null || string === undefined)
throw new Error('input must be castable to string')
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.
Good point. Should it throw for anything other than a string?
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.
In my opinion, yes.
I'd argue null or undefined as slugified should exactly an empty string. I think throwing on this would generally cause more issues than help. |
If undefined is passed in, this will return an empty string instead of an error. Not sure if this error is preferred to just returning an empty string though.