As I’m sure everyone is aware, Shotgun has stated they are not planning to implement field validation at this time. Personally, I have not yet accepted this outcome, and am in the “bargaining” phase of my grief.
Is it possible we’re not getting this much-needed feature because we pushed for something too complicated? Perhaps it makes sense to go back to square one and request only the most basic possible thing – a fixed set of simple regex patterns for fields.
Here’s a list of useful validations I came up with:
- ip address
- email address
- phone number
- file path
- folder name
- file name
- alphabetical with underscores
- alphanumeric with underscores
- alphabetical, followed by numerical
- numerical, followed by alphabetical
- valid maya object name (probably need a name for this)
The key is that these patterns would be provided out-of-the-box by Shotgun, and not a user-customizable regex system, or an elaborate hook system with awareness of multiple fields. BUT, you could combine some of these with calculated fields to stretch it a bit further.
Don’t get me wrong – this is extremely limited. However, I don’t think we should settle for nothing, just because we can’t have everything. And if I’m being honest, for a lot of the more complex cases, it probably makes more sense to build custom front end tools, and this is easier now with a REST API.
I’m curious what people think about this, and what other patterns they would want. Would a system like this be beneficial, even if it doesn’t solve all of the problems?