A frequent piece of feedback I get when changing a Swagger spec is that I'm not documenting min/max length and regex rules for certain string properties such as resource names. I should do this for documentation purposes, but I don't.

The reason I don't include regex constraints and the like is because AutoRest uses them to generate client-side validation code, which I don't want. It introduces too much coupling between the client and the service and makes versioning more painful for practically zero benefit. I expand more on this line of reasoning in the discussion in this PR.

Client-side validation can make sense in the context of a UI where round-trip time is important and you need to preserve the user's work, but in the context of a library that directly calls a REST API it makes little sense.