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.
This pull request refactors the consumer contract example and guide to use
ReceiverTemplateinstead ofIReceiverTemplate, and introduces several improvements to code clarity, security, and maintainability. The changes include renaming the abstract contract, updating all references, switching permission fields to private, adding getter functions and events, and enhancing documentation for metadata encoding. These updates make the contract interface more robust and easier to use for developers.Contract and API Refactoring
IReceiverTemplatetoReceiverTemplate, updated all inheritance and import statements, and replaced all references in documentation and code examples. [1] [2] [3] [4] [5] [6]forwarderAddress,expectedAuthor,expectedWorkflowName,expectedWorkflowId) from public to private, and provided public getter functions for each.ForwarderAddressUpdated,ExpectedAuthorUpdated,ExpectedWorkflowNameUpdated, andExpectedWorkflowIdUpdated, and emitted these events in the corresponding setter functions. [1] [2] [3]Security and Maintainability Improvements
Example and Guide Updates
CalculatorConsumer,MyConsumer,AdvancedConsumer) to inherit fromReceiverTemplate, use new field names, and update logic to match new API. [1] [2] [3] [4] [5]