Skip to content

Make JsonReadContext non-final #1421

Description

@isalvadori

After opening a discussion here about the need (or not) for the JsonReadContext to be final, it turned out there is no strong reason behind having it final.
Thus, I would like to propose to remove the final on that class.
This will allow easier customization of the context.

Activity

  1. maho7791 commented on Apr 24, 2025

    @maho7791

    I wanted to mention that we would need this also for the 3.x versions.
    We currently move our EMF mapping for jackson3.

  2. cowtowncoder commented on Apr 24, 2025

    @cowtowncoder
    Member

    Yes, we merge forward changes in most cases, and do so here.

  3. changed the title [-]Make `JsonReadContext` non final[/-] [+]Make `JsonReadContext` non-final[/+] on Apr 24, 2025
  4. added a commit that references this issue on Apr 24, 2025
    5d13d28
  5. added a commit that references this issue on Apr 24, 2025
    104f6b1
  6. maho7791 commented on Apr 24, 2025

    @maho7791

    This was faster than light!!!

  7. cowtowncoder commented on Apr 24, 2025

    @cowtowncoder
    Member

    @maho7791 fwtw this was due to lucky timing. It's not always this fast -- but sometimes that happens which is great :)

  8. added this to the 2.19.0 milestone on Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions