Make example string conform to regex

[dewijones92]

Description

Make the example string conform to the regex pattern

Motivation and Context

Otherwise the request body is invalid

How Has This Been Tested?

Created unit test for it

Screenshots (if appropriate):

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.

[dewijones92]

I have cleaned up the code

[dewijones92]

Rebased

[dewijones92]

Any particular reason why this isn't being merged in? Am I missing something?
thanks :)

[tim-lai]

@dewijones92 Thanks for the PR, it functionally works for me. However, can you update so that it passes the lint-errors test?

9:42  error  'generateStringFromRegex' was used before it was defined  no-use-before-define

[dewijones92]

@tim-lai I have amended
hope it is ok now? thanks

[dewijones92]

rebased

[tim-lai]

@dewijones92 PR merged! Thanks for the contribution!

[GandalfTheBlack16]

Hi there, I just opened an issue relative to this feature.., it's look like Swagger-ui now expects a @Schema Example attribute to be always specified, cause if you define a @pattern on your field but you dont specify an @Schema(example="") value something go wrong and try it out section is so verbose by 'error':

You can check the issue here: #8003

And the repo with a easily reproducible demo here: https://github.com/GandalfTheBlack16/demo-swagger

Thanks so much!

[tautvydasfrontit]

@tim-lai @dewijones92
In our project API models contains lots of regexp pattern such as this: "[\p{L}]+(['՚’＇֊᠆‐‑﹣－-]+[\p{L}]+)[.]?([\p{Zs}]+[\p{L}]+(['՚\’＇֊᠆‐‑﹣－-]+[\p{L}]+)[.]?)*".
Since now swagger-ui tries to generate value for each field marked with 'pattern', it causes slow UI behaviour and sometimes even crash browser. Both cases swagger-ui becomes unusable.
I would appreciate a way to disable this functionality or have a workaround, cause now it really troubles our workflow.

[sdunderdog]

If your app is Java application and using this internally I have had luck adding this annotation from io.swagger.v3.oas.annotations.media.Schema to override pattern value in UI.
@Schema(defaultValue = "the_default_value_you_like_to_see_in_swagger")