Closed atokuzAmzn closed 2 years ago
@mcliedtke Can you review this?
Can you also comment on what branches you believe this change to be added to. Are you targeting for updating 2.13?
@mcliedtke good catch on missing check. I have added the extra assertion. Yes we are targeting to update 2.13
LGTM, I think these changes can be merged. Given the nature of the change, I think merging to 2.13 is pretty safe. @cowtowncoder do you want to handle the merge itself?
@cowtowncoder or @mcliedtke Can we merge this into 2.13?
Following up with this merge request @cowtowncoder @mcliedtke
Ok, I am back from my vacation. @atokuzAmzn If you want this merged against 2.13, please rebase or recreate. While cherry-picking sometimes works, the usual practice is to start with the oldest branch & merge forward.
This is my first time working with github. I changed the base of this PR but I am not sure if this is what you wanted @cowtowncoder. If needed I can recreate a new PR based on 2.13
@atokuzAmzn Alas, no: this would merge back all changes from 2.14 -- and not just ones you are making -- so that wouldn't work. I am not 100% sure what'd be the easiest way to change the base for existing PR. Maybe others can suggest something?
But it may be easier to simply create a new PR, if that works?
I created a new PR based on 2.13 here : https://github.com/FasterXML/jackson-dataformats-binary/pull/322
This PR aims to resolve the issue https://github.com/FasterXML/jackson-dataformats-binary/issues/317
Changes: