Sourced from eosjs's releases.

EOSJS v22.1.0 Release Notes

This release is the stable release of EOSJS v22.1.0 and contains features, security, stability and miscellaneous fixes.

Support for Read Only Transactions

This release introduces support for the new feature of read only transactions within smart contracts. This feature provides a contract-supported method of read-only queries from external clients via HTTP-RPC. Prior to this release, access was limited to data stored in a single table in DB or KV tables via the get_table_rows or get_kv_table_rows API, a mechanism which is exacting and inefficient. Read-only queries enable developers to perform more complex, cross-table queries natively via contract code with the assurance that table data is from the same block height. It can also be used to understand the consequences of a transaction before it is sent. More information can be found here in the documentation for cleos and here in the documentation specific to eosjs.

The transaction_trace has been modified with the addition of a bill_to_accounts field, so that it is clear which account paid for cpu/net for the transaction. Additionally, in the case of a failed transaction, available traces are returned to assist in the understanding of why the transaction failed. You can find the failure traces by using the new details field in the RPCError object.

An example transaction using eosjs might look like:

await api.transact({
    actions: [{
        account: 'readonly',
        name: 'get',
        authorization: [{
            actor: 'readonly',
            permission: 'active',
        }],
        data: {},
    }],
}, {
    useLastIrreversible: true,
    expireSeconds: 30,
    readOnlyTrx: true,
    returnFailureTraces: true,
});

The above transaction calls this action that is able to retrieve entries in two tables instead of needing to run get_kv_table_rows multiple times:

[[eosio::action, eosio::read_only]]
std::vector<my_struct> get() {
   my_table_m tm{get_self()};
   my_table_f tf{get_self()};
std::vector<my_struct> ret;
auto itm = tm.id.begin();
auto itm_e = tm.id.end();
eosio::cout << "Males: \n";
while(itm != itm_e){
auto row = itm.value();
eosio::cout << "id=" << row.id << ", name=" << row.name << ",gender=" << row.gender << ", age=" << row.age << "\n";
my_struct s;
s.id = row.id;
s.name = row.name;
s.gender = row.gender;
s.age = row.age;
ret.push_back(s);
++itm;
</tr></table>

... (truncated)

• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.