Adding commonly used slugifying support to illuminate/support.

[bencorlett]

I've previously stated my objections to having a full-blown string class / package in Laravel 4 due to the fact that many applications do not require it and there are many, many different packages out there to cater for different needs.

However, I think slugifying strings is something many applications will use. Whether it be for your next simple blog post to have friendly URLs, or your next product management suite to give automatic SKUs to products (I could go on), most apps have a need to create a simple, URL friendly string.

I've done exactly this, by adding a Slugify class (open to suggestions on the name), with a str_slug() helper.

This PR relates to issue #69.

[drsii]

+1

[ipalaus]

I really only miss the slug function... +1 :)

[brunogaspar]

+1

[conradkleinespel]

👍 !

[dardub]

I use this one. +1

[darrennolan]

Agreed. I keep writing my own in every app I use.

[bencorlett]

@darrennolan - I had a feeling there was a few of us doing this!

[taylorotwell]

I think we need to consider introducing a String class into Support, and moving some of these helpers into said class.

[Anahkiasen]

I would be all for the String class to be brought back and all of the currently str_ helpers to be moved into it.

[taylorotwell]

I'm working on something to solve this.