Sometimes there are multiple ways a key can be captured. With 0.1.5 I get a list of the value and null. The new capturesFlattened cleans up multiple values as long as there is only one non-null value.
@anthonycorbacho I don't know if you like the additional capture Method. Or if you would prefer an option for the grok/matcher object itself? And what do you think about the exception, I'd like to warn the user about an ambiguity.
Sometimes there are multiple ways a key can be captured. With 0.1.5 I get a list of the value and null. The new capturesFlattened cleans up multiple values as long as there is only one non-null value.
@anthonycorbacho I don't know if you like the additional capture Method. Or if you would prefer an option for the grok/matcher object itself? And what do you think about the exception, I'd like to warn the user about an ambiguity.