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
Currently, the SDK interfaces are tightly coupled with the underlying contract interfaces. This results in breaking changes whenever contract interfaces are updated, even if the core functionality remains the same. To improve flexibility and maintainability, we should refactor the SDK to adopt a request-response pattern.
Proposed Solution
Introduce request structs to encapsulate input parameters.
Continue returning the Ethereum Receipt (from go-ethereum) instead of creating a custom response struct.
The text was updated successfully, but these errors were encountered:
damiramirez
changed the title
refactor: elcontracts/reader interface to use request-response pattern
refactor: elcontracts/writer interface to use request-response pattern
Feb 3, 2025
Currently, the SDK interfaces are tightly coupled with the underlying contract interfaces. This results in breaking changes whenever contract interfaces are updated, even if the core functionality remains the same. To improve flexibility and maintainability, we should refactor the SDK to adopt a request-response pattern.
Proposed Solution
request
structs to encapsulate input parameters.Updated methods:
elcontracts/writer
new interface for selected methods #507elcontracts/writer
new interface for selected methods #507elcontracts/writer
new interface for selected methods #507elcontracts/writer
new interface for selected methods #507elcontracts/writer
new interface for selected methods #507elcontracts/writer
new interface for selected methods #507elcontracts/writer
new interface for selected methods #507elcontracts/writer
new interface for selected methods #507elcontracts/writer
new interface for selected methods #507The text was updated successfully, but these errors were encountered: