You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is to request a feature. Lets say Client C calls a chaincode S, and that chaincode (using chaincode to chaincode call) invokes chaincode T, now if T sets some event, currently that event is lost, as per docs:
// Only a single event can be included in a transaction, and must originate
// from the outer-most invoked chaincode in chaincode-to-chaincode scenarios.
But I read that same transaction context is used to do chaincode to chaincode invocation, so why can't the event set in chaincode T be passed to the whole transaction, and thus that event can also be emitted (if S doesn't emit any other event later)?
This feature is very much required for a project that our team is working on.
The text was updated successfully, but these errors were encountered:
sandeepnRES
changed the title
Allow chaincode to chaincode invoke emit event
Allow chaincode to chaincode invoke set event
Nov 3, 2022
This is to request a feature. Lets say Client C calls a chaincode S, and that chaincode (using chaincode to chaincode call) invokes chaincode T, now if T sets some event, currently that event is lost, as per docs:
But I read that same transaction context is used to do chaincode to chaincode invocation, so why can't the event set in chaincode T be passed to the whole transaction, and thus that event can also be emitted (if S doesn't emit any other event later)?
This feature is very much required for a project that our team is working on.
The text was updated successfully, but these errors were encountered: