When using the "strict" mode in 1.4 (which is new as of that release), a case insensitive path extractor will throw on an error when it attempts to extract from a sequence with at least one element.
While arguably this is a case of mistyped data and should be an Exception, it is not backwards compatible to throw for this and the error is confusing.
Consider:
PathExtractor<PageExtractionContext> extractor = PathExtractorBuilder.<PageExtractionContext>standard()
.withMatchCaseInsensitive(true)
.withSearchPath("(foo)", callback)
.build(); // or buildStrict() to be explicit about it
extractor.match("[17]", context); // throws (pseudo-syntax)
When using the "strict" mode in 1.4 (which is new as of that release), a case insensitive path extractor will throw on an error when it attempts to extract from a sequence with at least one element.
While arguably this is a case of mistyped data and should be an Exception, it is not backwards compatible to throw for this and the error is confusing.
Consider: