fix: dspace 2024/1 compliant transformers #4581
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR changes/adds
dspace 2024/1 compliant transformers.
Duplicates all the dsp from transformers when needed for:
consumerPid
andproviderPid
as@id
participantId
in catalog as@id
assigner
andassignee
inContractAgreementMessage
as@id
state
as@id
inContractNegotiation
andTransferProcess
endpointType
in data address as@id
format
andagreementId
inTransferRequestMessage
as@id
eventType
inContractNegotiationEventMessage
as@id
state
inJsonObjectFromTransferProcessTransformer
transformed like theJsonObjectFromContractNegotiationTransformer
Why it does that
dsp 2024/1 compliance
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes #4577
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.