To include events in a smart contract schema, the developer needs to provide a single type representing all the possible events, which then implements SchemaType. This is usually done using (rust) enums. We provide a type Cis2Event in our smart contract library concordium-cis2, which represents the events logged as part of CIS-2. Now, if a smart contract logs events outside the events from CIS-2, the developer will need to implement the SchemaType manually for the type representing the contract events and requires the developer to reimplement some of the work we provide with Cis2Event.
This can be seen in the example for the wrapped CCD:
Additionally, the trait Serial and Deserial has to be implemented manually as well in this case.
To include events in a smart contract schema, the developer needs to provide a single type representing all the possible events, which then implements SchemaType. This is usually done using (rust) enums. We provide a type Cis2Event in our smart contract library concordium-cis2, which represents the events logged as part of CIS-2. Now, if a smart contract logs events outside the events from CIS-2, the developer will need to implement the SchemaType manually for the type representing the contract events and requires the developer to reimplement some of the work we provide with Cis2Event.
This can be seen in the example for the wrapped CCD:
Additionally, the trait Serial and Deserial has to be implemented manually as well in this case.