Currently, Dynamic Object patterns can match on;
digits [0-9]
letters [a-z]
alphanumeric [a-z0-9]
spaces [\s]
My platform can sometimes generate URLs which contain a double-slash "//" in part of the URL;
https://example.com/resources//123
I want to use Dynamic Objects to catch examples like this using a single matcher (i.e. matching either the "resources/:id" or "resources//:id" path), so it would be helpful to define matching on a "/" character (1 or 2).
Similarly, this would be useful in cases where URL parts could contain non-alphanumeric characters (like UUIDs)