Feat/trigger service #54
Merged
Conversation
This file contains 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
amimart
force-pushed
the
feat/trigger-service
branch
from
4409dde to
b9ae987
Compare
ccamel
approved these changes
Apr 19, 2022
ingvaar
approved these changes
Apr 19, 2022
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a new
trigger-servicetransaction.Purpose
The main goal of this first version of the
trigger-servicetransaction is to effectively trigger a service execution in reaction of this specific transaction.It is mainly oriented to serve test purposes and help in the design definition of a future production oriented version.
Details
The transaction contains only an
uriparameter meant to receive service reference & execution parameters. The trigger is not currently stored in the state.There is no strong validation as the services have actually no existence in the protocol.