feat: align ContractRequestMessage behavior #201
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jimmarino
approved these changes
Jun 27, 2025
Contributor
|
@juliapampus can you take a look at this? Thx. @wolf4ood can then sync the TCK. |
juliapampus
approved these changes
Jun 27, 2025
juliapampus
merged commit e298b2d
into
eclipse-dataspace-protocol-base:main
3 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
align ContractRequestMessage behavior by removing mandatory
callbackAddressandusing
oneOfforcallbackAddressfor initialContractRequestMessageproviderPidfor subsequentContractRequestMessageWhy it does that
Briefly state why the change was necessary.
Further notes
List other areas of the documents that have changed but are not necessarily linked to the main feature. This could be editorial changes or mistakes in example files that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes #200
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.