When working with views filters, the admin can specify if the database query is equal to, contains, starts with, or greater than the value provided. Both the operator and value can be exposed to the user. Contextual filters lack this function, and must be equal to the value provided. Is there a specific reason that this was left out? I have edited the core StringArgument to give it the same operators as the StringFilter. Is there a reason (security, feature overlap) that I shouldn't submit this as a feature addition?