Yearn optional chaining fix

What's Changed

• JB/Removes optional chaining on yearn bridge by @jonybur in #213

New Contributors

• @jonybur made their first contribution in #213

Full Changelog: v0.1.52...v0.1.53

BridgeDataFieldGetters.getAuxData(...) returns number[]

refactor: returning number[] from getAuxData(...) (#211)

* refactor: returning number[] from getAuxData(...)

* chore: version bump

Unified types with internal, Yearn client

Changes:

1. AssetValue is imported from barretenberg instead of using the local one,
2. since AssetValue in barretenberg was a bit different from the local one (value instead of amount, number assetId instead of bigInt) basically all the clients had to be refactored to reflect this,
3. added Yearn client,
4. refactored getAPR function to have only the vault asset on input,
5. Element client uses getTermAPR instead of getAPR function,
6. BridgeDataFieldGetters inteface was expanded withgetTermAPR.

Helper for underlying asset value

For bridges with wrapped assets, users often have a hard time figuring out what the value is or think that the wrapped asset and underlying has a value 1:1. To mitigate, we make a helper function on the bridge data class that allows frontends to get the value of the wrapped asset in the underlying, e.g., for wstEth outputs a value in stEth that can be displayed on the frontend.

Bug fix for retrieving latest block

This release fixes an issue in block retrieval under some providers

Element bridge data class update

v0.1.48

Merge pull request #139 from joss-aztec/jcf/interaction_present_value…

Curve bridge data

Merge pull request #133 from AztecProtocol/feat/curve-bridge-data

Curve steth bridge data

Curve wsteth bridge

v0.1.46

Bump version

Bump version number

Updates the package.json version

Lido Client Data

Updated the Lido Client data helper for frontends