github PolymeshAssociation/polymesh-sdk v10.0.0-beta.1

latest releases: v26.2.0-alpha.5, v26.2.0-alpha.4, v26.2.0-alpha.3...
pre-release3 years ago

10.0.0-beta.1 (2021-09-15)

Bug Fixes

  • 🐛 consider exceptions when converting TxTag to ProtocolOp (1427111)
  • 🐛 update polymesh types to latest 3.3.0 (8da6b90)

Features

  • 🎸 [WIP] upgrade types (56fe378)
  • 🎸 allow disabling IU when creating a token (3c8be1b)
  • 🎸 allow disabling IU when creating a token (02ccc03)
  • 🎸 feedback (f61c482)
  • add better support for third party fees (3d39cf1)
  • support new custom asset type system (3a122c6)
  • upgrade types to Mesh 3.3.0 (72a0cb5)

BREAKING CHANGES

  • 🧨 the SecurityTokenDetails interface now has a new
    requireInvestorUniqueness: boolean property. This affects the return
    value of SecurityToken.details
    • property tokenType of the TickerReservation.create method's parameters is now always a
      string. Custom types no longer need to be passed as { custom: <type> }, they will be
      detected automatically
    • change the return type of Identity.getPrimaryKey from string to Account
  • the tag property of PolymeshTransaction and PolymeshTransactionBatch can no longer be an
    empty string (it will always be set from the beginning)
  • remove the paidByThirdParty property of PolymeshTransaction and PolymeshTransactionBatch,
    in favor of the new getPayingAccount
  • change the behavior of TransactionQueue.getMinFees. The function now returns a FeeBreakdown
    object, which contains information on which fees have to be paid by the current Account, and
    which will be paid by other (third party) accounts, as well as respective balances and
    allowances. The previous version ignored third party fees entirely
  • make TransactionQueue.run throw errors if a third party paying Account doesn’t have enough
    balance/allowance to pay for the queue’s fees
  • 🧨 the SecurityTokenDetails interface now has a new
    requireInvestorUniqueness: boolean property. This affects the return
    value of SecurityToken.details
    • deprecate NoData, Custom, TransferPrimaryIssuanceAgent and TransferCorporateActionAgent
      authorization types. Attempting to accept/reject authorizations of these types will result in
      an error
  • throw a specific error when consuming an expired JoinIdentity or AddMultiSigSigner
    authorization
  • throw a specific error if attempting to run a Procedure that requires Identity roles without an
    Identity. Add a noIdentity property to the ProcedureAuthorizationStatus interface to
    reflect this scenario (affects the result of checkAuthorization in procedure methods)

Don't miss a new polymesh-sdk release

NewReleases is sending notifications on new releases.