Issue #20 Support for Account properties #46
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sill pending working tests
implementation of address account properties e2e test for address account properties creation + retrieval junit tests for account properties model
account properties are now implemented together with tests. supported account property types are allow/block address/mosaic/transactionType
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixing issue #20 - account properties are now supported by the SDK
supported account property types are allow/block for address/mosaic/transactionType. There is also Sentinel type which does not seem to be supported by go or ts SDKs so I will ignore it for the time being. Raised issue #45 to handle the sentinel type.