Skip to content

Conversation

@benvmatheson
Copy link

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.

slug.js Outdated

function slug(string, opts) {
string = string.toString();
string = (string || '').toString();
Copy link
Author

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?

Copy link
Contributor

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')

Copy link
Author

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?

Copy link
Contributor

Choose a reason for hiding this comment

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

In my opinion, yes.

@benvmatheson benvmatheson changed the title Give empty string in place of undefined Throw error if null or undefined May 31, 2016
@lillem4n
Copy link

lillem4n commented Jan 5, 2018

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.

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.

3 participants