-
Notifications
You must be signed in to change notification settings - Fork 432
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
Persist Environment
in metadata
#1741
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1741 +/- ##
==========================================
- Coverage 70.76% 70.67% -0.10%
==========================================
Files 206 206
Lines 6455 6581 +126
==========================================
+ Hits 4568 4651 +83
- Misses 1887 1930 +43
... and 56 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@@ -16,7 +16,6 @@ categories = ["no-std", "embedded"] | |||
include = ["Cargo.toml", "src/**/*.rs", "README.md", "LICENSE"] | |||
|
|||
[dependencies] | |||
ink_metadata = { version = "4.1.0", path = "../metadata", default-features = false, features = ["derive"], optional = true } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed this because it seems it is not used anywhere.
* sr25519 signature verification * offchain signature verification * fmt * schnorrkel optional * update dictionary * fix * update changelog * add info about unstable function usage * missing docs * review suggestions * added catch for invalid public key or signature in sr25519 verification public key byte[] and/or signature byte[] may not be constructed into a PublicKey or Signature if it's in the wrong format. These errors originate from the schnorrkel library and need to be caught, otherwise it'll panic and propagate up to smart contracts in ink. * switched to simple signing context in sr25519_verify fn there is no need to make the context directly, we can delegate that to the schnorrkel library * Added docs for sr25519_verify() Docs + example + notes about context set to "substrate" * Added docs to sr25519VerifyFailed error Helpful for debugging why the error has occurred, as there is only ever one of 3 reasons: invalid public key, invalid message or invalid signature * Added docs link to substrate sr25519 signing context * cargo fmt * Remove reference on message variable of sr25519_verify() Not required according to clippy * Clippy embed error in panic statement during metadata execution Clippy's advice * sr25519 verification tests Tested invalid public key, invalid signature, invalid message and valid case * Updated sr25519_verify PR number in CHANGELOG.md * Fix comment to adhere to spell check in sr25519 verification tests * add parity as author of sr25519 module Co-authored-by: Green Baneling <[email protected]> * ignore semicolon correction in item module * add warning to docs for sr25519_verify() depending on unstable interfaces * remove space typo from sr25519 docs * remove #1741 from changelog * added documentation to the dummy method in sr25519_verification example * typo in sr25519 example contract dummy method * spell check fix in method doc for sr25519 * spell check fix in method doc for sr25519 * move changelog entry for #1741 * changelog typo --------- Co-authored-by: kziemianek <[email protected]> Co-authored-by: Green Baneling <[email protected]>
This PR closes #1695 by adding a field
environment
tometadata.json
which contains the info about the types of the contract's environment.