Non final JsonReadContext

[isalvadori]

Hi all,
we are trying out jackson 3 rc2.
I just would like to know why is the JsonReadContext final? Its counter part, JsonWriteContext is not.
We are working on a unified framework to read/write EMF object from/into other formats and we would like to be able to extend the contexts, in such a way to also store additional, EMF-related information. While we are able to do it during writing, the fact that the JsonReadContext is final makes it harder to write something which just treats the json case like all the others.
Is there any particular reason why that class is marked as final or can you make non final?

[cowtowncoder]

I don't remember strict reason for it having to be final: if you could file an issue against jackson-core to request change, this can be done for upcoming 2.19.0 (cannot change in a patch wrt semantic versioning).

[isalvadori]

OK, thanks. Then I will file the issue.