Releases: elven-js/elven.js
Releases · elven-js/elven.js
v0.6.2
- added new callbacks for transactions
onTxSent
andonTxError
. WithonTxSent
, you can get the transaction data before it is finalized on the chain and after signing it. Then you can useonTxFinalized
. Check the source code of the demo example. - dependencies updates
v0.6.1
- make the WalletConnect bridge addresses configurable. You can use
ElvenJS.init({ walletConnectBridgeAddresses: ['https://...'], })
to overwrite the default ones.
v0.6.0
- Elrond Web Wallet support
- new way of getting the last transaction status, you can now use a callback function defined when initializing the ElvenJS:
onTxFinalized: (tx) => { ... }
. Check for more info in the docs. You can still use the return value fromawait ElvenJS.signAndSendTransaction(tx)
, but it won't work for the Web Wallet (because of its redirections and different flow). - there is also another callback to handle transactions states:
onTxStarted: (tx) => { ... }
- the
ElvenJS.init
now always returns undefined. You should rely on its callbacks from now on instead of returned booleans - some refactoring around walletconnect provider configuration
v0.5.0
- a couple of login fixes
- Breaking change: Now you can pass not only the id for the QR container but also the DOM element, so there are changes in how you should define it. New way:
await ElvenJS.login('maiar-mobile', { qrCodeContainer: <elem_id_as_string_or_DOM_element>});
v0.4.0
onLoggedIn
,onLoginPending
andonLogout
callbacks are now passed in theElvenJS.init()
function. This unifies it and helps in synchronizing the WalletConnect actions. In the future probably also Ledger integration will be simpler because of that.- added a smart contract query (for now, without result parsing tools, it will probably be a separate library, you can still parse the result manually for simple data types like string or number, check the example/index.html)
- exported
AddressValue
- example demo updates (example demo)
v0.3.3
- additional exports from erdjs required for esdt/sft/nft/meta sending (
ESDTNFTTransferPayloadBuilder
,ESDTTransferPayloadBuilder
) - Updated demo. By default, you can send a predefined ESDT token
v0.3.2
- fix type export
- add Solid.js demo
v0.3.1
- fix types export, export login methods enum
v0.3.0
- breaking change: from v0.3.0, the elven.js is served as an ES6 module. Why? Because ES6 modules are well supported in all browsers, it will be much simpler to make it compatible with many different frontend frameworks if needed. It would be simpler to import it from node_modules. You can still use it directly from the CDN. You just need to import it using
<script type="module" />
Check the docs for more info about it. - supporting it as a standard script seems to be obsolete nowadays, but please let me know if you have a good use case for it, then I will try to support both
v0.2.0
- Maiar mobile app auth functionality with QR code generation
- changes for the init function, you don't set the auth provider anymore. It is moved to the login function
- a lot of refactoring