Closed dj8yfo closed 3 months ago
commit https://github.com/near/cargo-near/pull/162/commits/ca135003f059c24b531fde89967e1a36e9c96f8b was lost in merge of https://github.com/near/cargo-near/pull/159, as it was accidentally not pushed to remote before merge, which was discovered when testing on contract
SIDENOTE: commit https://github.com/near/cargo-near/pull/162/commits/787c3a429e24957101f44857e3f33ea4c8e906cb fixes somewhat unrelated problem, also present in main . It can be cherry-picked into a standalone pr to main :
main
as cargo metadata is called without any additional args (--features or whatnot), the following diff:
cargo metadata
--features
-near-sdk = { version = "5.1.0", features = ["legacy"], git = "https://github.com/dj8yfo/near-sdk-rs.git", branch = "add_contract_metadata" } +near-sdk = { version = "5.1.0", default-features = false, features = ["wee_alloc", "legacy"], git = "https://github.com/dj8yfo/near-sdk-rs.git", branch = "add_contract_metadata" }
results in
Error: 0: `near-sdk` dependency must have the `abi` feature enabled
which somewhat contradicts no explicit abi feature , which is promoted for use by near-docs
abi
commit https://github.com/near/cargo-near/pull/162/commits/ca135003f059c24b531fde89967e1a36e9c96f8b was lost in merge of https://github.com/near/cargo-near/pull/159, as it was accidentally not pushed to remote before merge, which was discovered when testing on contract
SIDENOTE: commit https://github.com/near/cargo-near/pull/162/commits/787c3a429e24957101f44857e3f33ea4c8e906cb fixes somewhat unrelated problem, also present in
main
. It can be cherry-picked into a standalone pr tomain
:as
cargo metadata
is called without any additional args (--features
or whatnot), the following diff:results in
which somewhat contradicts no explicit
abi
feature , which is promoted for use by near-docs