Skip to content

refactor: split AbstractJsonLdTransformer into 2 different collaborators #5334

@ndr-brt

Description

@ndr-brt

Feature Request

AbstractJsonLdTransformer has become too much to handle, it avoids some duplication but it does not provide abstract features that could make the json-ld transformation easier. Actual transformers are still not easy to test.

My proposal would be to have 2 different services:

  • JsonLdSerializer (to be used in the JsonObjectFrom...Transformers)
  • JsonLdDeserializer (to be used in the JsonObjectTo...Transformers)

that will be user

Which Areas Would Be Affected?

e.g., DPF, CI, build, transfer, etc.

Why Is the Feature Desired?

Are there any requirements?

Who will sponsor this feature?

Please @-mention the committer that will sponsor your feature.

Solution Proposal

If possible, provide a (brief!) solution proposal.

Metadata

Metadata

Assignees

No one assigned

    Labels

    refactoringCleaning up code and dependencies

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions