allow more characters in model name (and number)

[peelman]

I assume the restrictiveness is a side effect of #57. Not sure what the best solution is here. But right now, you can't even edit the seed data because the validation will fail (seed models include ( ) and ,).

If it were me, I would validate their presence and that's it, but I don't know what other concerns you already ran into that had you add the validators in the first place.

[snipe]

The validators are there to reduce risk of XSS. Laravel does a nice job of escaping data on the way out, but I've run into a few jquery plugins in this project that reversed that escaping, actually re-assembling the HTML encoding and making it vulnerable. There's just no reason to use < or > in this data, so I'm validating against it. I'll find a better balance of characters to filter out - that custom validate was my first stab at writing a custom validator in this framework, so I expect to massage the particulars over time. In general, whitelisting is a better approach than blacklisting, IMHO. Takes longer, but more thorough.

[snipe]

Fixed in 33f81ab