While testing, we found a bug that when using the MaxLength or MinLength analyzers with the NullBehavior.EmptyString analyzer option, we weren't properly emitting metrics when using a where filter.
This was because the filter was not properly applied to constructing the criterion.
This PR fixes this issue for both MaxLength and MinLength analyzers and adds tests to verify.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Issue #, if available:
Description of changes:
MaxLengthorMinLengthanalyzers with theNullBehavior.EmptyStringanalyzer option, we weren't properly emitting metrics when using a where filter.filterwas not properly applied to constructing the criterion.MaxLengthandMinLengthanalyzers and adds tests to verify.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.