Skip to content

MetadataTransactionService requires to define a maxFee #656

@dgarcia360

Description

@dgarcia360
Contributor

metadataService.createAccountMetadataTransaction function now requires to pass a maxFee, but the param should be optional. Having maxFee as an optional param is especially useful when defining inner aggregate transactions.

Activity

added
P3 IssueLow severity cosmetic issues with minor inconvenience
and removed
P3 IssueLow severity cosmetic issues with minor inconvenience
on Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @rg911@dgarcia360

        Issue actions

          MetadataTransactionService requires to define a maxFee · Issue #656 · symbol/symbol-sdk-typescript-javascript