Native: unify arguments naming of CryptoLib's verifyWith* methods#3855
Native: unify arguments naming of CryptoLib's verifyWith* methods#3855
verifyWith* methods#3855Conversation
`verifyWithEd25519` was recently added in #3507 and is a part of Echidna, but its argument naming convention differs from the one we have in `verifyWithECDsa`. This change is reflected in the CryptoLib's manifest, so it's nice when we have a unified naming in native contract manifest. Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
cschuchardt88
left a comment
There was a problem hiding this comment.
Why are you changing to non-standard naming convention? Changing this name doesn't make it any easier for users to understand what the name means. Everything needs to be spelled out and obvious what it does. We all agreed on this. See neo-project/.github#8 for information on this agreement.
|
neo/src/Neo/SmartContract/Native/CryptoLib.cs Line 115 in af9371a neo/src/Neo/SmartContract/Native/NeoToken.cs Line 367 in af9371a neo/src/Neo/SmartContract/Native/NeoToken.cs Line 396 in af9371a This one is about manifest-level (NEP-15) consistency, not C# naming. It has precedence because it has some well-established names and these names are much harder to change (HF required). |
|
Names need to be aligned with what they do and be obvious. VM assembly code does not care about the names. Names are just for guidance. The only thing that cares is the manifest and it's as a label nothing more. |
Port neo-project/neo#3855. Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
* master: (163 commits) [style] Added some var styles (neo-project#3867) [`fix`] stop syncing on block 1465790 (neo-project#3888) Optimize block deserialization (neo-project#3879) Avoid double `ToArray` on `OnInvMessageReceived` (neo-project#3875) style: format long lines (neo-project#3884) optimize: return GetFileNameWithoutExtension(Path) if name is not set (neo-project#3883) Fix possible null exception (neo-project#3880) Remove linkedList (neo-project#3873) Optimize Uint160 and Uint256 constructor (neo-project#3872) Release the resources (neo-project#3868) [Clean] Remove `IRawReadOnlyStore` (neo-project#3869) move non-plugins out of plugins (neo-project#3863) feature: set name when create wallet (neo-project#3866) Native: swap Policy's `[get/set]AttributeFee` implementations (neo-project#3859) Fix: concurrent conflict in Cache.CopyTo (neo-project#3860) Fix: add default key parameter in help cmd (neo-project#3865) [Plugin UT] add more rpcserver UTs (neo-project#3864) config: upgrade NeoFS chains protocol configuration (neo-project#3858) [`Optimization`]: add exception message to `ArgumentException` (neo-project#3862) Native: unify arguments naming of CryptoLib's `verifyWith*` methods (neo-project#3855) ... # Conflicts: # benchmarks/Neo.VM.Benchmarks/OpCode/Arrays/OpCode.ReverseN.cs # benchmarks/Neo.VM.Benchmarks/Program.cs # src/Neo/Neo.csproj # src/Neo/ProtocolSettings.cs # src/Neo/SmartContract/ApplicationEngine.cs # src/Neo/SmartContract/Native/NeoToken.cs # src/Neo/SmartContract/Native/RoleManagement.cs # tests/Neo.UnitTests/SmartContract/Manifest/UT_ContractManifest.cs # tests/Neo.UnitTests/SmartContract/Manifest/UT_ContractPermission.cs # tests/Neo.UnitTests/SmartContract/Native/UT_NativeContract.cs # tests/Neo.UnitTests/SmartContract/Native/UT_NeoToken.cs # tests/Neo.UnitTests/UT_ProtocolSettings.cs # tests/Neo.VM.Tests/UT_ReferenceCounter.cs
…eo-project#3855) `verifyWithEd25519` was recently added in neo-project#3507 and is a part of Echidna, but its argument naming convention differs from the one we have in `verifyWithECDsa`. This change is reflected in the CryptoLib's manifest, so it's nice when we have a unified naming in native contract manifest. Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru> Co-authored-by: NGD Admin <154295625+NGDAdmin@users.noreply.github.com>
Description
verifyWithEd25519was recently added in #3507 and is a part of Echidna, but its argument naming convention differs from the one we have inverifyWithECDsa. This change is reflected in the CryptoLib's manifest and is a part of the node's state, so it's nice when we have a unified naming in native contract manifest.Discovered when porting #3507 to NeoGo. It's not a critical change, but unification is always good.
Type of change
How Has This Been Tested?
Checklist: