-
Notifications
You must be signed in to change notification settings - Fork 285
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.
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
fix(plugin-ledger-connector): Some of the plugin-ledger-connectors are using wrong Interface Types in their class definitions #1445
Comments
Research needs to be done on why the compiler is okay with this and if there's any configuration parameter that would make it so that it does error out. Enforcing these things manually will always be a doomed effort so ideally we'd somehow find a way to have the CI do the heavy lifting instead. |
Totally agree on this: The compiler should throw error to show to the outside that the required interface type and the implemented type are not matching |
@petermetz: Can you please assign this issue to me |
According to my suggestion I will create a branch named "NOT_fixed_1445_for_reproduction_DONT_UPDATE" and a branch for the fix that we can have as sonn as possible a fixed version and in parallel can do researches on the un-fixed branch to find out why the linter / compiler is not complaining |
@m-courtin Sounds good to me. My only nit: keep branches all lower-case if possible. (some git tooling/operating systems do not take kindly to certain edge cases that stem from mixed-case branch names) |
@petermetz Ok fine, I'll use lower-case only for my branch names |
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: #1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
For all the connector class definitions the implementation are fixed to follow their interface definition and to match in consistent way for all the connectors Closes: hyperledger-cacti#1445 Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
Describe the bug
Some of the plugin-ledger-connectors are using wrong Interface Types in their class definitions where the types for the deployContract() and the transact() functions are getting defined.
To Reproduce
In plugin-ledger-connector-quorum for example the class definition needs to implement "IPluginLedgerConnector<
DeployContractSolidityBytecodeV1Request, DeployContractSolidityBytecodeV1Response,
RunTransactionRequest, RunTransactionResponse >" but the deployContract() is using DeployContractSolidityBytecodeV1Request and RunTransactionResponse instead of the interface definition pair DeployContractSolidityBytecodeV1Request, DeployContractSolidityBytecodeV1Response.
Similar is the case for the besu connector.
Expected behavior
For all the connector class definitions the implementation needs to follow their interface definition and need to match in consistent way for all the connectors.
The text was updated successfully, but these errors were encountered: