-
-
Notifications
You must be signed in to change notification settings - Fork 812
Allow FilteringParserDelegate to skip last elements in array #883
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow FilteringParserDelegate to skip last elements in array #883
Conversation
Ok, one quick question first: would it make sense to rebase against Also: before merging I'd need CLA (unless I have received one before -- apologies if I missed it). CLA is from here: https://github.com/FasterXML/jackson/blob/master/contributor-agreement.pdf The usual way is to print the doc, fill & sign, scan/photo, email to Thank you again for contributing this -- looking forward to merging it ASAP! |
@cowtowncoder I believe you have a corporate CLA for Elastic. |
@cowtowncoder I can either rebase this PR against 2.14 and forward-port it to 2.15 What is the preferred way in fasterxml project? |
target 2.14 and then we'll merge to 2.15 and master |
…bject of array was excluded
Adds 1 new test to BasicParserFilteringTest, and switches the implementation of all testExcludeObject* methods to build on existing Jackson testing infrastructure.
2eb2fc9
to
476c48e
Compare
I had a feeling I should have CCLA for Elastic but for some reason I don't seem to be able to locate it. |
Given that there should be CLA in effect & there will be updated one sent, I will merge this now. |
FilteringParserDelegate when parsing ID_END_ARRAY or ID_END_OBJECT of the skipped element (when
_headContext.isStartHandled() == false
should be able to exit the loop and continue parsing next tokens.This logic was changed accidentally removed in 7db467d#diff-f6642caef61e0c403f51a6150ecf45263034fca5002782fd02eacd01e53fe549L694
closes #882