common-regex VS logstash-patterns

comparitor.insert("iyr", Regex::new(r"^(201[0-9]|2020)$").unwrap());

There are lots of number parsing.

I would enable both [[:1-12:]] and [[:01-12:]] as options without / with leading zeros.

About the variables:

This file would look much more readable with variables that are reusing other regexes:

https://github.com/spcan/common-regex/blob/3238bc8ee85e0e000...

Why don't languages have grok patterns in their standard libraries?

It seems to only exist in log parsing ecosystems but this really helps with getting rid of little bugs and wrong parsing of specific regex patterns.

Instead of doing "^\d+(\.\d+){3}$" for IP checking which is clearly wrong, you'd do "%{IPV4:ip}" which is so much better.

List of known patterns : https://github.com/hpcugent/logstash-patterns/blob/master/fi...

Even for PHP a third party library only has 15 stars.

in case you haven't, it can be found here. https://github.com/hpcugent/logstash-patterns/blob/master/files/grok-patterns

Also, some of the patterns can be referred from https://github.com/hpcugent/logstash-patterns/blob/master/files/grok-patterns I personally prefer the above link for constructing grok pattern.