Skip to content

Type parsers conflict #2363

Closed
Closed
@vitaly-t

Description

@vitaly-t

When your application uses multiple third-party modules, each initialized from reusable Pool, is there any provision as to how to deal with each module trying to set its own type parsers?

From what I see, we are getting nothing but conflicts in this scenario, as parsers are set on a singleton. Is there any solution to this that I'm not aware of?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions