Add regex support to data generator using FARE

[Crown0815]

Nuget Package

JsonSchema.Net.DataGeneration

Package Version

Newest

Can this library make doing something simpler?

according to the documentation, Regex Generation is not supported. Using the FARE library it should be easy to add proper support for it.

https://github.com/moodmosaic/Fare/tree/master

Describe alternatives you've considered.

No response

Is there any other information you'd like to share regarding this enhancement?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[gregsdennis]

Thanks for the suggestion. I think this is one of the many that I looked at when I was putting the library together. Everything seemed to have some limitations.

I can take another look, though. It looks like the only update it's received in the past 6 years has been to support netstandard2.0 instead of 2.1. That raises questions of support.

Also, if I recall, one of the hard parts was figuring out how to combine the boolean options for regex. For example, if I have an anyOf where each of the subschemas have a pattern keyword, then I need to generate a string that can meet at least one of the regexes. That's not too hard. However, if I have a oneOf, then I need to generate a string that meets only one of the regexes. That's a lot harder because I have to create a single regex that basically says

• a and not b and not c, or
• not a and b and not c, or
• not a and not b and c

I had found some answers of how to build that with regex on StackOverflow, and I found that I could create the regex (I might still have the branch, too), but I didn't find any data generators that would support them.

[Crown0815]

@gregsdennis, hmm, those are cases I was not aware of.
My team and I recently invested some time in example generation from JSON schemas in .NET and came across the FARE project which served our purpose.

While not supporting all cases, would using the FARE library not serve to solve a majority of cases? It would at lease allow to reduce the amount of unsupported cases.

From our side, supporting basic „pattern“ bases string properties would already be great.

mir would you say, that if regex is supported, it should either be supported 100% or not at all?

[gregsdennis]

I'll look into adding basic support in, but I don't think I want to account for the multiple-subschema cases I described above. I think throwing an exception if a pattern is found inside a *Of might be acceptable.

[Crown0815]

I think throwing an exception if a pattern is found inside a *Of might be acceptable.

I agree. Those are not „simple“ regex, but far more complicated to properly handle.