prevent exceptions with empty and- and or-qualifiers in ERXPrefixQualifierTraversal #675
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Wonder it is legal to create empty ERXAndQualifier and ERXOrQualifiers. This is convenient when creating complex qualifiers dynamically, which depend on user input and whether certain sub-qualifiers shall be included or not.
However when trying to prefix a qualifier structure, which contains empty ERXAndQualifier and ERXOrQualifiers, an exception is thrown due to an invalid NSRange. Sample code (both lines generate an exception):
This patch solves the issue in ERXPrefixQualifierTraversal.