I see. That might be an issue with the validation implementation. Would you mind filing a ticket on Swagger-UI (not Swgger-Editor)?
From: <[email protected]> on behalf of Greg Fox <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, May 1, 2018 at 13:28 To: Swagger <[email protected]> Subject: Re: Regex /i Option Support This is happening in the Swagger Editor running in the browser when I do a Try it Out. With the /i option on the end of the regex, Uppercase, Lowercase & Mixed case entries in the field all fail. If I remove the /I, then the Uppercase will work but not Lowercase or Mixed case. On Tuesday, May 1, 2018 at 2:19:08 PM UTC-5, Ron wrote: It doesn’t seem to work where? Swagger is a set of tools, not a specific one. Which tool are you referring to? From: <[email protected]> on behalf of Greg Fox <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Friday, April 20, 2018 at 14:19 To: Swagger <[email protected]> Subject: Regex /i Option Support I am trying to use a regex that contains the "/i" option to make the entire regex case insensitive. For some reason this doesn't seem to work. I do see it in the ECMA 262 (2011) specification so it should work. Am I using this option incorrectly for the Swagger regex implementation? '^[A-Z0-9][A-Z0-9-]+[A-Z0-9]$/i' -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
