Skip to content

doc: add caveat for setEvent in nested invocations #502

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bestbeforetoday merged 1 commit into from
Mar 12, 2026
+1 −0
Merged

doc: add caveat for setEvent in nested invocations #502

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions libraries/fabric-shim/lib/stub.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -763,6 +763,7 @@ class ChaincodeStub {
* Only a single chaincode event can be included in a transaction.
* If setEvent() is called multiple times only the last event will be included in the transaction.
* The event must originate from the outer-most invoked chaincode in chaincode-to-chaincode scenarios.
* If Chaincode A invokes Chaincode B, and Chaincode B calls setEvent, that event will be ignored by the peer.
* The marshaled ChaincodeEvent will be available in the transaction's ChaincodeAction.events field.
* @param {string} name Name of the event
* @param {byte[]} payload A payload can be used to include data about the event
Expand Down
Loading